Date:	Fri, 19 Nov 1999 16:46:07 +0100
From:	Marc Lehmann <pcg AT opengroup DOT org>
To:	pgcc AT delorie DOT com
Cc:	Charl DOT Botha AT crusader DOT co DOT za
Subject:	Re: pgcc + Tillamook 266 problems
Message-ID:	<19991119164607.B4788@cerebro.laendle>
Mail-Followup-To:	pgcc AT delorie DOT com, Charl DOT Botha AT crusader DOT co DOT za
References:	<D766E2598838D31181B300105A6BEABD09CFBB AT SBSERVER>
Mime-Version:	1.0
In-Reply-To:	<D766E2598838D31181B300105A6BEABD09CFBB@SBSERVER>; from Charl Botha on Fri, Nov 19, 1999 at 10:06:46AM +0200
X-Operating-System:	Linux version 2.2.13 (root AT cerebro) (gcc version 2.95.1 19990816 (release))
Reply-To:	pgcc AT delorie DOT com
X-Mailing-List:	pgcc AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Fri, Nov 19, 1999 at 10:06:46AM +0200, Charl Botha <Charl DOT Botha AT crusader DOT co DOT za> wrote:
>    generates an "illegal instruction" error on a Tillamook (mobile
>    pentium mmx) 266MHz and then coredumps, but not on the Celerons that

And it does coredump on the exact same occurences, i.e. is the coredump
reproducable with the same file? Or does it happen always?

And did you test it against the same files on the celeron?

>    The code was compiled with -O3.  Are there any *known* problems with

Is that the only switch?

>    pgcc-2.95-2 (I think) and the intel Tillamook processors?

No. But there is the possibility that your compile by default compiled
code for the p-ii cpus, which have a different instruction set. This is
unlikely, however, and depends on how pgcc was configured.

-- 
      -----==-                                             |
      ----==-- _                                           |
      ---==---(_)__  __ ____  __       Marc Lehmann      +--
      --==---/ / _ \/ // /\ \/ /       pcg AT opengroup DOT org |e|
      -=====/_/_//_/\_,_/ /_/\_\       XX11-RIPE         --+
    The choice of a GNU generation                       |
                                                         |

- Raw text -