public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andries.Brouwer@cwi.nl
To: jakub@redhat.com
Cc: alan@lxorguk.ukuu.org.uk, bernds@redhat.com,
	linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: gcc-2.95.2-51 is buggy
Date: Fri, 24 Nov 2000 13:48:14 +0100 (MET)	[thread overview]
Message-ID: <UTC200011241248.NAA138093.aeb@aak.cwi.nl> (raw)

> so the reason why it did not show up in the gcc you picked up from
> ftp.gnu.org is that you have compiled it so that it defaults to -mcpu=i686

Yes, you are right.

So 2.95.2 fails for i386, i486, i586 and does not fail for i686.

Andries
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2000-11-24 14:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-24 12:48 Andries.Brouwer [this message]
2000-11-24 16:46 ` gcc-2.95.2-51 is buggy Matthew Vanecek
  -- strict thread matches above, loose matches on Subject: below --
2000-11-27 14:28 Pavel Pisa;research student
2000-11-24 13:04 Mikael Pettersson
2000-11-24  8:09 Frédéric L . W . Meunier
2000-11-24  5:20 Andries.Brouwer
2000-11-24  5:44 ` Neil Brown
2000-11-24  6:47   ` Alexander Viro
2000-11-25 17:26   ` Rik van Riel
2000-11-25 19:16     ` Jeff V. Merkey
2000-11-25 20:01     ` Andries Brouwer
2000-11-25 20:06       ` Rik van Riel
2000-11-26 15:33         ` Olaf Dietsche
2000-11-26 16:58           ` Rik van Riel
2000-11-26 19:36           ` Mike Castle
2000-11-26 19:41             ` Russell King
2000-11-26 19:55           ` J . A . Magallon
2000-11-24  9:37 ` Ion Badulescu
2000-11-24 10:18   ` Linux Kernel Developer
2000-11-24  9:57 ` Jakub Jelinek

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=UTC200011241248.NAA138093.aeb@aak.cwi.nl \
    --to=andries.brouwer@cwi.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bernds@redhat.com \
    --cc=jakub@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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