public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Christian Casteyde <casteyde.christian@free.fr> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/6199: Internal Compiler Error while compiling Wine with gcc-20020401 Date: Mon, 08 Apr 2002 10:06:00 -0000 [thread overview] Message-ID: <20020408170600.9035.qmail@sources.redhat.com> (raw) The following reply was made to PR c/6199; it has been noted by GNATS. From: Christian Casteyde <casteyde.christian@free.fr> To: rodrigc@gcc.gnu.org, casteyde.christian@free.fr, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: c/6199: Internal Compiler Error while compiling Wine with gcc-20020401 Date: Mon, 8 Apr 2002 19:06:00 +0200 On Monday 8 April 2002 03:20, you wrote: > State-Changed-From-To: open->feedback > State-Changed-By: rodrigc > State-Changed-When: Sun Apr 7 18:20:28 2002 > State-Changed-Why: > Submit preprocessed source as mentioned in: > http://gcc.gnu.org/bugs.html > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc& >pr=6199 I submitted it to neil@daikokuya.demon.co.uk in my first answer, but I hadn't managed to add it to the bug report after sending it through gnatsweb. Sorry, I didn't have the preprocessed source here, I cannot resend it to you. Neil should have received it. Will send it the next week to you if you want it. CC
next reply other threads:[~2002-04-08 17:06 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-08 10:06 Christian Casteyde [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-04-11 9:56 Christian Casteyde 2002-04-11 5:22 jakub 2002-04-07 18:20 rodrigc 2002-04-06 0:56 Neil Booth 2002-04-06 0:26 casteyde.christian
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=20020408170600.9035.qmail@sources.redhat.com \ --to=casteyde.christian@free.fr \ --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).