public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/111075] [14 Regression] ICE on g++.dg/torture/tail-padding1.C on darwin Date: Wed, 27 Mar 2024 15:30:57 +0000 [thread overview] Message-ID: <bug-111075-4-B5td3HqCxh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111075-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111075 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I can reproduce with a cross, doesn't ICE with -Os -fno-elide-constructors, on x86_64-linux doesn't ICE with/without -Os -f{,no-}elide-constructors. The ICE is on 3025 /* We used to shortcut trivial constructor/op= here, but nowadays 3026 we can only get a trivial function here with -fno-elide-constructors. */ 3027 gcc_checking_assert (!trivial_fn_p (fun) 3028 || !flag_elide_constructors 3029 /* We don't elide constructors when processing 3030 a noexcept-expression. */ 3031 || cp_noexcept_operand); where fun is X::X(X const&) and is trivial.
next prev parent reply other threads:[~2024-03-27 15:30 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-19 14:16 [Bug c++/111075] New: " fxcoudert at gcc dot gnu.org 2023-08-19 14:17 ` [Bug c++/111075] " fxcoudert at gcc dot gnu.org 2023-09-08 20:52 ` fxcoudert at gcc dot gnu.org 2024-03-04 13:01 ` [Bug c++/111075] [14 Regression] " rguenth at gcc dot gnu.org 2024-03-07 23:24 ` law at gcc dot gnu.org 2024-03-13 13:26 ` mpolacek at gcc dot gnu.org 2024-03-27 15:30 ` jakub at gcc dot gnu.org [this message] 2024-03-27 16:30 ` [Bug c++/111075] [13/14 " jakub at gcc dot gnu.org 2024-03-27 17:36 ` jakub at gcc dot gnu.org 2024-05-21 9:16 ` [Bug c++/111075] [13/14/15 " jakub 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-111075-4-B5td3HqCxh@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).