Summary: | sys-devel/gcc[lto]: bootstrap comparison failure | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Stephan Hartmann (RETIRED) <sultan> |
Component: | Current packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | herrtimson |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | gcc build logs |
Description
Stephan Hartmann (RETIRED)
![]() sys-devel/gcc-9.5.0 looks similar sys-devel/gcc:9.5.0[lto] works with "-march=commetlake -mno-avx512f". Trying now remaining flags: @@ -12 +12 @@ - -mabm [disabled] + -mabm [enabled] @@ -24 +24 @@ - -march= cannonlake + -march= icelake-client @@ -54 +54 @@ - -mclwb [disabled] + -mclwb [enabled] @@ -78 +78 @@ - -mgfni [disabled] + -mgfni [enabled] @@ -103,2 +103,2 @@ - -mmovdir64b [disabled] - -mmovdiri [disabled] + -mmovdir64b [enabled] + -mmovdiri [enabled] @@ -122 +122 @@ - -mpconfig [disabled] + -mpconfig [enabled] @@ -130 +130 @@ - -mptwrite [disabled] + -mptwrite [enabled] @@ -132 +132 @@ - -mrdpid [disabled] + -mrdpid [enabled] @@ -144 +144 @@ - -msgx [enabled] + -msgx [disabled] @@ -146 +146 @@ - -mshstk [disabled] + -mshstk [enabled] @@ -174 +174 @@ - -mvaes [disabled] + -mvaes [enabled] @@ -177 +177 @@ - -mvpclmulqdq [disabled] + -mvpclmulqdq [enabled] @@ -179 +179 @@ - -mwaitpkg [disabled] + -mwaitpkg [enabled] With gcc-9 the situation is very weird. It succeeds with -march=native and -mtune=generic and fails with -march=native and -mtune=native. However, the target and parameter specific options are identical, because gcc-9 has no support for alderlake. With gcc-11.3 it succeeds with -march=native (-march=alderlake) and -mtune=generic, but still succeeds if I add target and parameter specific options. It only fails if I flip -mtune=generic to -mtune=alderlake. Any hints how to debug this further? (In reply to Stephan Hartmann from comment #3) > With gcc-9 the situation is very weird. It succeeds with -march=native and > -mtune=generic and fails with -march=native and -mtune=native. However, the > target and parameter specific options are identical, because gcc-9 has no > support for alderlake. > With gcc-11.3 it succeeds with -march=native (-march=alderlake) and > -mtune=generic, but still succeeds if I add target and parameter specific > options. It only fails if I flip -mtune=generic to -mtune=alderlake. Any > hints how to debug this further? I'd probably take this to gcc bugzilla at this point. Could ask in #gcc on OFTC for hints too. (In reply to Sam James from comment #4) > (In reply to Stephan Hartmann from comment #3) > > With gcc-9 the situation is very weird. It succeeds with -march=native and > > -mtune=generic and fails with -march=native and -mtune=native. However, the > > target and parameter specific options are identical, because gcc-9 has no > > support for alderlake. > > With gcc-11.3 it succeeds with -march=native (-march=alderlake) and > > -mtune=generic, but still succeeds if I add target and parameter specific > > options. It only fails if I flip -mtune=generic to -mtune=alderlake. Any > > hints how to debug this further? > > I'd probably take this to gcc bugzilla at this point. Could ask in #gcc on > OFTC for hints too. |