public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ebotcazou@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, hpa@transmeta.com,
nobody@gcc.gnu.org
Subject: Re: c/7689: Bad code generated when function sometimes does not return
Date: Mon, 25 Nov 2002 13:16:00 -0000 [thread overview]
Message-ID: <20021119115222.24764.qmail@sources.redhat.com> (raw)
Synopsis: Bad code generated when function sometimes does not return
State-Changed-From-To: open->feedback
State-Changed-By: ebotcazou
State-Changed-When: Tue Nov 19 03:52:21 2002
State-Changed-Why:
I can't reproduce the problem with the testcase you provided (using -Os, -O0, -O1, -O2, -O3). Could you specify the options you passed to the compiler ?
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7689
next reply other threads:[~2002-11-19 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-25 13:16 ebotcazou [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-23 21:29 neroden
2002-08-22 15:06 hpa
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=20021119115222.24764.qmail@sources.redhat.com \
--to=ebotcazou@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=hpa@transmeta.com \
--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: 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).