This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/12709] [3.4 regression] ICE with __FUNCTION__ and function-try-block
- From: "bangerth at dealii dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 21 Oct 2003 15:25:17 -0000
- Subject: [Bug c++/12709] [3.4 regression] ICE with __FUNCTION__ and function-try-block
- References: <20031021145227.12709.ncm-nospam@cantrip.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12709
bangerth at dealii dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|critical |normal
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
Last reconfirmed|0000-00-00 00:00:00 |2003-10-21 15:25:16
date| |
Summary|crash on __noreturn__ in ?: |[3.4 regression] ICE with
|in try block |__FUNCTION__ and function-
| |try-block
Target Milestone|--- |3.4
------- Additional Comments From bangerth at dealii dot org 2003-10-21 15:25 -------
I don't think the crash has anything to do with __noreturn__. Here's
something smaller:
--------------------
void fun()
try
{
__FUNCTION__;
}
catch (...) {}
---------------------
g/x> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -c x.cc
x.cc: In function `void fun()':
x.cc:6: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
This seems like a bad interaction of __FUNCTION__ and a function-try
block.
It's a regression on mainline, in any case.
W.