public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: reichelt@igpm.rwth-aachen.de To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, klaas.decanniere@pandora.be, nobody@gcc.gnu.org Subject: Re: c/8518: Segmentation fault in gcc when compiling mplayer Date: Wed, 20 Nov 2002 05:06:00 -0000 [thread overview] Message-ID: <20021113221842.20985.qmail@sources.redhat.com> (raw) Synopsis: Segmentation fault in gcc when compiling mplayer State-Changed-From-To: open->analyzed State-Changed-By: reichelt State-Changed-When: Wed Nov 13 14:18:41 2002 State-Changed-Why: Confirmed. A smaller testcase is the following: ----------------------snip here------------------ extern inline int foo () { return 0; } extern inline int bar () { return 0; } static inline int bar () { return foo(); } ----------------------snip here------------------ Just compile with "gcc -O -c" to see the ICE. The bug is present in gcc 3.1 - 3.2.1 and mainline. It is a regression from gcc 3.0.x where the code compiled fine. Thus, "high priority". http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8518
next reply other threads:[~2002-11-13 22:18 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-20 5:06 reichelt [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-22 10:26 ebotcazou 2002-11-10 12:16 klaas.decanniere
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=20021113221842.20985.qmail@sources.redhat.com \ --to=reichelt@igpm.rwth-aachen.de \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=klaas.decanniere@pandora.be \ --cc=nobody@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).