public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Gwenole Beauchesne <gbeauchesne@mandrakesoft.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/6323: GCC 3.1 regression from previous snapshot Date: Tue, 16 Apr 2002 06:26:00 -0000 [thread overview] Message-ID: <20020416132606.631.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/6323; it has been noted by GNATS. From: Gwenole Beauchesne <gbeauchesne@mandrakesoft.com> To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, mark@codesourcery.com, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, jason@redhat.com Cc: Subject: Re: optimization/6323: GCC 3.1 regression from previous snapshot Date: Tue, 16 Apr 2002 15:21:21 +0200 Hi, Sirs, sorry for having concatenated your e-mail addresses in the original report. ;-) FWIW, the error message from GNU C++ version 3.1 20020401 (prerelease) is different from the 2002/04/16 snapshot: In file included from ../../../libjava/include/jvm.h:110: ../../../libjava/exception.cc: At global scope: ../../../libjava/exception.cc:28: Internal compiler error in expand_call_inline , at tree-inline.c:898 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. It works with GNU C++ version 3.1 20020325 (prerelease). http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6323
next reply other threads:[~2002-04-16 13:26 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-16 6:26 Gwenole Beauchesne [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-04-18 10:28 mmitchel 2002-04-17 0:06 Gwenole Beauchesne 2002-04-16 18:55 rth 2002-04-16 18:11 rth 2002-04-16 6:56 Gwenole Beauchesne 2002-04-16 6:06 gbeauchesne
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=20020416132606.631.qmail@sources.redhat.com \ --to=gbeauchesne@mandrakesoft.com \ --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).