public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/100786] [9/10/11/12 Regression] ICE: in fold_convert_loc with alias attribute and different types and different sizes Date: Fri, 10 Dec 2021 02:52:24 +0000 [thread overview] Message-ID: <bug-100786-4-2etdfNLjHW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100786-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100786 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |ice-on-invalid-code Status|UNCONFIRMED |NEW Last reconfirmed| |2021-12-10 Target Milestone|--- |9.5 Known to fail| |11.1.0, 4.9.0, 5.1.0 Known to work| |4.7.1, 4.8.5 Ever confirmed|0 |1 Summary|ICE: in fold_convert_loc |[9/10/11/12 Regression] |with alias attribute and |ICE: in fold_convert_loc |different types and |with alias attribute and |different sizes |different types and | |different sizes --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Can also reproduce using the following code with the C++ front-end: extern const double a = 0; extern int b __attribute__((alias("a"))); int inc() { b++; } Confirmed. I think the alias should be rejected if the following is true: (TREE_CODE (a) == FUNCTION_DECL) != (TREE_CODE (b) == FUNCTION_DECL) || (sizeof (a) != sizeof (b))
next prev parent reply other threads:[~2021-12-10 2:52 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-27 1:28 [Bug c/100786] New: ICE: in fold_convert_loc, at fold-const.c:2429 cnsun at uwaterloo dot ca 2021-05-27 3:19 ` [Bug middle-end/100786] ICE: in fold_convert_loc with alias attribute and different types and different sizes pinskia at gcc dot gnu.org 2021-12-10 2:52 ` pinskia at gcc dot gnu.org [this message] 2022-01-20 13:29 ` [Bug middle-end/100786] [9/10/11/12 Regression] " rguenth at gcc dot gnu.org 2022-01-20 15:50 ` cvs-commit at gcc dot gnu.org 2022-01-20 15:51 ` [Bug middle-end/100786] [9/10/11 " rguenth at gcc dot gnu.org 2022-02-17 9:06 ` cvs-commit at gcc dot gnu.org 2022-04-21 12:52 ` [Bug middle-end/100786] [9/10 " cvs-commit at gcc dot gnu.org 2022-05-06 11:08 ` [Bug middle-end/100786] [9 " cvs-commit at gcc dot gnu.org 2022-05-06 11:11 ` 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-100786-4-2etdfNLjHW@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).