public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Craig Rodrigues <rodrigc@mediaone.net> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/5337: gcc-3.0.3 gives internal error Date: Sun, 13 Jan 2002 10:26:00 -0000 [thread overview] Message-ID: <20020113182601.2560.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/5337; it has been noted by GNATS. From: Craig Rodrigues <rodrigc@mediaone.net> To: Teemu Hirsimaki <Teemu.Hirsimaki@hut.fi> Cc: rodrigc@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: c++/5337: gcc-3.0.3 gives internal error Date: Sun, 13 Jan 2002 13:25:05 -0500 On Sun, Jan 13, 2002 at 10:15:18AM +0200, Teemu Hirsimaki wrote: > rodrigc@gcc.gnu.org writes: > > Btw, should I reply to all these addresses which were in the reply-to > field of your mail? Yes, you need to do that. That is how we keep track of the bug reports. > I tried different optimization flags, and "-finline-functions" seems > to trigger the bug. At the configure stage, if I configure my gcc with --enable-checking, I can reproduce your bug if I add -finline-functions to the command-line. If I omit the --enable-checking at the configure step, or add --disable-checking, then even if I add -finline-functions to the command-line, I cannot reproduce the bug.
next reply other threads:[~2002-01-13 18:26 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-13 10:26 Craig Rodrigues [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-01 20:21 paolo 2002-01-13 0:16 Teemu Hirsimaki 2002-01-12 17:39 rodrigc
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=20020113182601.2560.qmail@sources.redhat.com \ --to=rodrigc@mediaone.net \ --cc=gcc-prs@gcc.gnu.org \ --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).