linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: rmk@arm.linux.org.uk (Russell King)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
	philb@gnu.org (Philip Blundell),
	junio@siamese.dhis.twinsun.com, manuel@mclure.org (Manuel McLure),
	linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.3-ac12
Date: Sun, 22 Apr 2001 14:29:51 +0100 (BST)	[thread overview]
Message-ID: <E14rJw2-0005r5-00@the-village.bc.nu> (raw)
In-Reply-To: <20010422142224.D20807@flint.arm.linux.org.uk> from "Russell King" at Apr 22, 2001 02:22:24 PM

> On Sun, Apr 22, 2001 at 02:10:41PM +0100, Alan Cox wrote:
> > 	Recommended
> > 	-----------
> > 	egcs-1.1.2		(miscompiles strstr  <2.4.4pre)
> > 	gcc 2.95.*		(miscompiles strstr  <2.4.4pre)
> 
> Aren't both of these "miscompilation" problems are referring to the file
> arch/i386/lib/strstr.c?  Therefore, its an x86 problem.  To use a phrase
> that Linus uses, "its not an interesting problem" for the other
> architectures.

In theory the strstr miscompile might bite any other architecture with a 
braindead set of string instructions, a ludicrously low register count and
inlined strsr. So yes its x86 only

The recommended compilers for non x86 are different too - eg you need
2.96 gcc for IA64, you need 2.95 not egcs for mips and so on.


  reply	other threads:[~2001-04-22 13:28 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-22  2:53 Linux 2.4.3-ac12 Alan Cox
2001-04-22  4:17 ` Manuel McLure
2001-04-22  5:47   ` junio
2001-04-22  6:07   ` junio
2001-04-22 10:42   ` Philip Blundell
2001-04-22 12:26     ` Alan Cox
2001-04-22 12:43       ` Philip Blundell
2001-04-22 12:54         ` Alan Cox
2001-04-22 13:00           ` Philip Blundell
2001-04-22 13:10             ` Alan Cox
2001-04-22 13:22               ` Russell King
2001-04-22 13:29                 ` Alan Cox [this message]
2001-04-22 16:12                   ` Jes Sorensen
2001-04-22 16:30                     ` Mohammad A. Haque
2001-04-22 17:27                     ` Roman Zippel
2001-04-22 17:43                       ` Jes Sorensen
2001-04-22 18:42                     ` Alan Cox
2001-04-23  6:54                     ` Geert Uytterhoeven
2001-04-22 13:51               ` Philip Blundell
2001-04-22 12:11   ` Alan Cox
2001-04-22 12:18     ` Russell King
2001-04-22 12:51       ` Alan Cox
2001-04-22 12:55     ` John Jasen
2001-04-22 13:00       ` Alan Cox
2001-04-22  8:57 ` Eyal Lebedinsky
2001-04-22 12:20   ` Alan Cox
2001-04-22 13:04     ` Eyal Lebedinsky
2001-04-22 16:25 ` John Cavan
2001-04-22 17:07   ` Manuel McLure
2001-04-22 18:48     ` Alan Cox
2001-04-22 18:57       ` Manuel McLure
2001-04-22 18:59       ` Linux 2.4.3-ac12 unresolved symbol rwsem J Sloan
2001-04-23  0:19       ` Linux 2.4.3-ac12 John Cavan
2001-04-23  8:35       ` Byeong-ryeol Kim
2001-04-23 22:18         ` Byeong-ryeol Kim
2001-04-22 22:46 ` Mr. James W. Laferriere
2001-04-22 13:48 f5ibh
2001-04-22 14:03 ` Jesper Juhl
2001-04-22 17:26 Dieter Nützel
2001-04-22 19:53 ` J . A . Magallon

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=E14rJw2-0005r5-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=junio@siamese.dhis.twinsun.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manuel@mclure.org \
    --cc=philb@gnu.org \
    --cc=rmk@arm.linux.org.uk \
    /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 NNTP newsgroup(s).