public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/108086] [11/12/13 Regression] internal compiler error: in set_accesses, at rtl-ssa/internals.inl:449 Date: Fri, 16 Dec 2022 11:32:31 +0000 [thread overview] Message-ID: <bug-108086-4-z5clu4j23q@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108086-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108086 --- Comment #13 from Richard Biener <rguenth at gcc dot gnu.org> --- (In reply to Richard Biener from comment #12) > A regression from GCC 10 which compiles this in 90s at -O1. > > Richard? Can you please look at this special-case of BB0 insn_info? The following might be one way to "fix" it (until we do a bigger testcase) diff --git a/gcc/rtl-ssa/insns.h b/gcc/rtl-ssa/insns.h index f7215972845..b0144f258b2 100644 --- a/gcc/rtl-ssa/insns.h +++ b/gcc/rtl-ssa/insns.h @@ -403,8 +403,7 @@ private: // MAX_RECOG_OPERANDS is the maximum number of pseudos that can be // defined by an instruction, so the number of definitions should fit // easily in 16 bits. - unsigned int m_num_uses; - unsigned int m_num_defs : 16; + unsigned int m_num_uses : 24; // Flags returned by the accessors above. unsigned int m_is_debug_insn : 1; @@ -412,9 +411,13 @@ private: unsigned int m_is_asm : 1; unsigned int m_has_pre_post_modify : 1; unsigned int m_has_volatile_refs : 1; + // For future expansion. + unsigned int m_spare : 3; + // Keep 32bit aligned + unsigned int m_num_defs : 24; // For future expansion. - unsigned int m_spare : 11; + unsigned int m_spare : 8; // The program point at which the instruction occurs. //
next prev parent reply other threads:[~2022-12-16 11:32 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-13 18:40 [Bug c++/108086] New: " jonas.keller@uni-bielefeld.de 2022-12-13 18:42 ` [Bug c++/108086] " jonas.keller@uni-bielefeld.de 2022-12-13 18:43 ` jonas.keller@uni-bielefeld.de 2022-12-13 18:43 ` jonas.keller@uni-bielefeld.de 2022-12-14 8:35 ` [Bug rtl-optimization/108086] " rguenth at gcc dot gnu.org 2022-12-14 8:47 ` rguenth at gcc dot gnu.org 2022-12-14 10:53 ` marxin at gcc dot gnu.org 2022-12-15 10:30 ` rguenth at gcc dot gnu.org 2022-12-15 10:32 ` cvs-commit at gcc dot gnu.org 2022-12-15 17:43 ` cvs-commit at gcc dot gnu.org 2022-12-16 8:30 ` cvs-commit at gcc dot gnu.org 2022-12-16 9:29 ` cvs-commit at gcc dot gnu.org 2022-12-16 11:27 ` [Bug rtl-optimization/108086] [11/12/13 Regression] " rguenth at gcc dot gnu.org 2022-12-16 11:32 ` rguenth at gcc dot gnu.org [this message] 2022-12-16 12:06 ` cvs-commit at gcc dot gnu.org 2022-12-16 18:21 ` rsandifo at gcc dot gnu.org 2023-02-02 10:41 ` rsandifo at gcc dot gnu.org 2023-02-02 14:53 ` cvs-commit at gcc dot gnu.org 2023-04-03 8:57 ` [Bug rtl-optimization/108086] [11/12 " cvs-commit at gcc dot gnu.org 2023-04-14 13:15 ` [Bug rtl-optimization/108086] [11 " hubicka at gcc dot gnu.org 2023-05-29 10:07 ` jakub at gcc dot gnu.org 2024-02-19 13:43 ` rguenth at gcc dot gnu.org 2024-06-04 12:48 ` cvs-commit at gcc dot gnu.org 2024-06-04 12:50 ` rsandifo 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-108086-4-z5clu4j23q@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).