https://gcc.gnu.org/bugzilla/show_bug.cgi?id=123619
--- Comment #9 from Haochen Jiang <haochen.jiang at intel dot com> --- (In reply to Haochen Jiang from comment #4) > I met a similar build fail for 523.xalancbmk_r with -Ofast -march=native > -flto on nearly on all machines include Granite Rapids, Sierra Forest, > Sapphire Rapids, Ice Lake, Zen5 and also on AWS Graviton3/4. > > during IPA pass: cp > lto1: internal compiler error: in decide_about_value, at ipa-cp.cc:6039 > 0x23bc96c internal_error(char const*, ...) > ../../gcc/diagnostic-global-context.cc:787 > 0x9c2025 fancy_abort(char const*, int, char const*) > ../../gcc/diagnostics/context.cc:1805 > 0x20696a1 decide_about_value<ipa_polymorphic_call_context> > ../../gcc/ipa-cp.cc:6039 > 0x20696a1 decide_whether_version_node > ../../gcc/ipa-cp.cc:6238 > 0x206c4a6 ipcp_decision_stage > ../../gcc/ipa-cp.cc:6550 > 0x206c4a6 ipcp_driver > ../../gcc/ipa-cp.cc:6746 > 0x206c4a6 execute > ../../gcc/ipa-cp.cc:6823 > Please submit a full bug report, with preprocessed source (by using > -freport-bug). > Please include the complete backtrace with any bug report. > See <https://gcc.gnu.org/bugs/> for instructions. > lto-wrapper: fatal error: g++ returned 1 exit status > > The build fail is build from r16-6654 (20260109), most likely 1/8 Daily Bump > is ok since someone (my colleague, not me) has run SPEC with that day GCC. > > Going to verify it on 1/8 trunk find which commit leads to the issue. Current trunk is ok for me. Thx for the fix.
