public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rassahah@neofonie.de
To: gcc-gnats@gcc.gnu.org
Subject: optimization/9324: gcc-3.4 segfaults combination of O2/functionptr/return val/argument/inline
Date: Wed, 15 Jan 2003 11:16:00 -0000 [thread overview]
Message-ID: <20030115111252.2974.qmail@sources.redhat.com> (raw)
>Number: 9324
>Category: optimization
>Synopsis: gcc-3.4 segfaults combination of O2/functionptr/return val/argument/inline
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: ice-on-legal-code
>Submitter-Id: net
>Arrival-Date: Wed Jan 15 03:16:01 PST 2003
>Closed-Date:
>Last-Modified:
>Originator: Rasmus Hahn
>Release: gcc-3.4 cvs
>Organization:
>Environment:
Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.4/specs
Configured with: : (reconfigured) : (reconfigured)
Thread model: posix
gcc version 3.4 20030115 (experimental)
>Description:
gcc-3.4 segfaults on how-to-repeat-program.
compiler-3.4-failureb.c: In function `callfunc':
compiler-3.4-failureb.c:11: internal compiler error: Segmentation fault
Please submit a full bug report,...
The bug occurs also if
- the function pointer is embedded in a structure
- values have some useful values. This scenario comes from linux-kernel 2.4.19-pre8,
kernel/signal.c where the function names are/were different.
It does not crash if
- the parameter of callfunc is removed, though not used
- no inline is used
- callfunc does not return a value
This bug is new in gcc-3.4, maybe has something to do with PR9298, maybe not
>How-To-Repeat:
typedef void (*func)();
inline func getfunc()
{
return (func) 3;
}
int callfunc(int foo) /* works without parameter */
{
getfunc () ();
return 0; /* works without return */
}
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
reply other threads:[~2003-01-15 11:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030115111252.2974.qmail@sources.redhat.com \
--to=rassahah@neofonie.de \
--cc=gcc-gnats@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).