public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/107232] New: [13 regression] insertion out of range in 'bit_insert_expr' breaks SPARC bootstrap Date: Wed, 12 Oct 2022 10:39:24 +0000 [thread overview] Message-ID: <bug-107232-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107232 Bug ID: 107232 Summary: [13 regression] insertion out of range in 'bit_insert_expr' breaks SPARC bootstrap Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: ro at gcc dot gnu.org CC: avieira at gcc dot gnu.org Target Milestone: --- Target: sparc-sun-solaris2.11 Between 20221010 (248c8aeebc49aae3fd96bd587367d12e7c8b3c3a) and 20221011 (576d524559776ee6744f478da600939ca5c2d502), Solaris/SPARC bootstrap broke with /vol/gcc/src/hg/master/local/gcc/ipa-sra.cc: In member function 'virtual void ipa_sra_function_summaries::duplicate(cgraph_node*, cgraph_node*, isra_func_summary*, isra_func_summary*)': /vol/gcc/src/hg/master/local/gcc/ipa-sra.cc:388:1: error: insertion out of range in 'bit_insert_expr' 388 | ipa_sra_function_summaries::duplicate (cgraph_node *, cgraph_node *, | ^~~~~~~~~~~~~~~~~~~~~~~~~~ _ifc__128 = BIT_INSERT_EXPR <_ifc__39, 0, 18446744073709551584 (1 bits)>; /vol/gcc/src/hg/master/local/gcc/ipa-sra.cc:388:1: error: insertion out of range in 'bit_insert_expr' _ifc__130 = BIT_INSERT_EXPR <_ifc__128, 0, 18446744073709551585 (1 bits)>; /vol/gcc/src/hg/master/local/gcc/ipa-sra.cc:388:1: error: insertion out of range in 'bit_insert_expr' _ifc__75 = BIT_INSERT_EXPR <_ifc__130, 0, 18446744073709551586 (1 bits)>; during GIMPLE pass: ifcvt /vol/gcc/src/hg/master/local/gcc/ipa-sra.cc:388:1: internal compiler error: verify_gimple failed /vol/gcc/src/hg/master/local/gcc/lra.cc: In function 'void setup_operand_alternative(lra_insn_recog_data_t, const operand_alternative*)': /vol/gcc/src/hg/master/local/gcc/lra.cc:803:1: error: position plus size exceeds size of referenced object in 'bit_field_ref' 803 | setup_operand_alternative (lra_insn_recog_data_t data, | ^~~~~~~~~~~~~~~~~~~~~~~~~ _ifc__33 = BIT_FIELD_REF <_ifc__32, 1, 18446744073709551602>; during GIMPLE pass: ifcvt /vol/gcc/src/hg/master/local/gcc/lra.cc:803:1: internal compiler error: verify_gimple failed in stage 3. This patch commit 25413fdb2ac24933214123e24ba165026452a6f2 Author: Andre Vieira <andre.simoesdiasvieira@arm.com> Date: Tue Oct 11 10:49:27 2022 +0100 vect: Teach vectorizer how to handle bitfield accesses seemed like a likely culprit, and indeed reverting it locally allowed the build to succeed.
next reply other threads:[~2022-10-12 10:39 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-12 10:39 ro at gcc dot gnu.org [this message] 2022-10-12 10:39 ` [Bug tree-optimization/107232] " ro at gcc dot gnu.org 2022-10-12 11:02 ` marxin at gcc dot gnu.org 2022-10-14 7:20 ` rguenth at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-107232-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).