The X86ScheduleGRT.td file is automatically generated by schedtool
(D130897). Some of instruction's scheduling information is based on
measured ADL-P data in uops.info.
Details
- Reviewers
- None
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
llvm/lib/Target/X86/X86.td | ||
---|---|---|
1082 | As I know, GRT is the common abbreviation for Gracemont in Intel. | |
llvm/lib/Target/X86/X86ScheduleGRT.td | ||
73 | Max lat for ADD (R32 M32) is 5 in uops.info. The extra load latency is 4. | |
537 | Instructions using this schedule write may be overwrite by InstRW. |
This model is not yet complete, we still miss lots of port/lat. (see // FIXME: Incompleted schedwrite. and GRTPortInvalid)
Should we rename alderlake-p to other name like alderlake-pc. Alder Lake P is also product series name (https://www.intel.com/content/www/us/en/products/platforms/details/alder-lake-p.html).
Adding extra aliases is cheap (e.g. sandybridge vs corei7-avx etc.), but we can keep the alderlake-p as the default
Imo GMT is more sensible than GRT.