public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "P.Grassberger" <p.grassberger@fz-juelich.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/9526: Internal compiler error Date: Sat, 01 Feb 2003 16:06:00 -0000 [thread overview] Message-ID: <20030201160601.30381.qmail@sources.redhat.com> (raw) The following reply was made to PR c/9526; it has been noted by GNATS. From: "P.Grassberger" <p.grassberger@fz-juelich.de> To: ehrhardt@mathematik.uni-ulm.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, p.grassberger@fz-juelich.de, gcc-gnats@gcc.gnu.org Cc: Subject: Re: c/9526: Internal compiler error Date: Sat, 01 Feb 2003 17:02:05 +0100 I forgot to say that I complied with "gcc -O5", no other options. I don't get an error without optimization, but I do get one also with "gcc -O". ehrhardt@mathematik.uni-ulm.de wrote: > > Synopsis: Internal compiler error > > State-Changed-From-To: open->feedback > State-Changed-By: cae > State-Changed-When: Sat Feb 1 14:43:42 2003 > State-Changed-Why: > I can't reproduce this either. Could you at least provide us > with somewhat more detailed instruction on how to repeat the bug > an the text of the Internal compiler error message that you got? > > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9526 -- Peter Grassberger John-von-Neumann Institute for Computing Forschungszentrum Juelich D-52425 Juelich, Germany Tel +49-2461-61-2326 Fax +49-2461-61-2430 e-mail p.grassberger@fz-juelich.de
next reply other threads:[~2003-02-01 16:06 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-01 16:06 P.Grassberger [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-09 22:46 Dara Hazeghi 2003-02-01 14:43 ehrhardt 2003-01-31 18:56 pme 2003-01-31 15:26 p.grassberger
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=20030201160601.30381.qmail@sources.redhat.com \ --to=p.grassberger@fz-juelich.de \ --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).