public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/106099] [13 Regression] ICE in execute_todo, at passes.cc:2134 since r13-1204-gd68d366425369649
Date: Mon, 04 Jul 2022 10:12:38 +0000 [thread overview]
Message-ID: <bug-106099-4-ZMm8LJr44L@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106099-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106099
--- Comment #5 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #3)
> (In reply to Martin Liška from comment #2)
> > Started with r13-1204-gd68d366425369649.
>
> Since -funreachable-traps is a new option, is this a regression then?
I have a new test-case that does not need the option:
$ cat new-alias.cpp
using size_t = decltype(sizeof(0));
extern "C" char *something(long long x) {}
void *operator new(size_t) __attribute__((alias("something")));
int *pr16715 = new int;
$ g++ new-alias.cpp -c -Og
new-alias.cpp: In function ‘char* something(long long int)’:
new-alias.cpp:2:42: warning: no return statement in function returning non-void
[-Wreturn-type]
2 | extern "C" char *something(long long x) {}
| ^
new-alias.cpp: At global scope:
new-alias.cpp:3:7: warning: ‘void* operator new(size_t)’ alias between
functions of incompatible types ‘void*(size_t)’ {aka ‘void*(long unsigned
int)’} and ‘char*(long long int)’ [-Wattribute-alias=]
3 | void *operator new(size_t) __attribute__((alias("something")));
| ^~~~~~~~
new-alias.cpp:2:18: note: aliased declaration here
2 | extern "C" char *something(long long x) {}
| ^~~~~~~~~
during GIMPLE pass: local-pure-const
new-alias.cpp: In function ‘void __static_initialization_and_destruction_0()’:
new-alias.cpp:4:23: internal compiler error: in execute_todo, at passes.cc:2140
4 | int *pr16715 = new int;
| ^
0x17450d1 execute_todo
/home/marxin/Programming/gcc/gcc/passes.cc:2140
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.
next prev parent reply other threads:[~2022-07-04 10:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 6:52 [Bug tree-optimization/106099] New: ICE in execute_todo, at passes.cc:2134 asolokha at gmx dot com
2022-06-27 9:04 ` [Bug tree-optimization/106099] " zsojka at seznam dot cz
2022-06-27 9:07 ` [Bug tree-optimization/106099] [13 Regression] ICE in execute_todo, at passes.cc:2134 since r13-1204-gd68d366425369649 marxin at gcc dot gnu.org
2022-06-27 9:18 ` pinskia at gcc dot gnu.org
2022-06-27 10:48 ` rguenth at gcc dot gnu.org
2022-07-04 10:10 ` marxin at gcc dot gnu.org
2022-07-04 10:12 ` marxin at gcc dot gnu.org [this message]
2022-07-04 11:35 ` jakub at gcc dot gnu.org
2022-07-04 11:38 ` jakub at gcc dot gnu.org
2022-07-26 10:25 ` jakub at gcc dot gnu.org
2022-07-28 10:43 ` cvs-commit at gcc dot gnu.org
2022-07-30 8:22 ` zsojka at seznam dot cz
2022-08-26 7:29 ` cvs-commit at gcc dot gnu.org
2022-10-18 13:02 ` jakub at gcc dot gnu.org
2023-01-03 11:23 ` 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-106099-4-ZMm8LJr44L@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: link
Be 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).