public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Neil Booth <neil@daikokuya.demon.co.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: [casteyde.christian@free.fr: Re: c/6199: Internal Compiler Error while compiling Wine with gcc-20020401]
Date: Fri, 12 Apr 2002 10:06:00 -0000	[thread overview]
Message-ID: <20020412170601.26840.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/6199; it has been noted by GNATS.

From: Neil Booth <neil@daikokuya.demon.co.uk>
To: gcc-gnats@gcc.gnu.org
Cc: Christian Casteyde <casteyde.christian@free.fr>
Subject: [casteyde.christian@free.fr: Re: c/6199: Internal Compiler Error while compiling Wine with gcc-20020401]
Date: Fri, 12 Apr 2002 17:35:12 +0100

 ----- Forwarded message from Christian Casteyde <casteyde.christian@free.fr> -----
 
 Subject: Re: c/6199: Internal Compiler Error while compiling Wine with gcc-20020401
 From: Christian Casteyde <casteyde.christian@free.fr>
 To: Neil Booth <neil@daikokuya.demon.co.uk>
 Date: Sat, 6 Apr 2002 19:50:31 +0200
 
 >
 > > >How-To-Repeat:
 > >
 > > Compile Wine 20020310 snapshot
 >
 > If we downloaded software for every bug we investigated, we'd never
 > get anything else done.
 
 Sorry.
 Here is the preprocessed file. Don't know how to reintroduce
 it in Gnats web (c/6199), so I send it by mail to you.
 
 Seems that it's an optimize bug finally.
 
 To reproduce :
 
 gcc -O2 -march=pentiumpro selector.i
 
 (compile nice without either -O2 or -march).
 
 
 CC
 
 
 
 ----- End forwarded message -----


                 reply	other threads:[~2002-04-12 17:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20020412170601.26840.qmail@sources.redhat.com \
    --to=neil@daikokuya.demon.co.uk \
    --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: 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).