Date:	Sat, 22 Jul 2000 10:35:57 +0200
From:	Marc Lehmann <pcg AT goof DOT com>
To:	pgcc AT delorie DOT com
Subject:	Re: Problems compiling kernel with pgcc 2.95.2
Message-ID:	<20000722103557.B665@cerebro.laendle>
Mail-Followup-To:	Marc Lehmann <pcg AT goof DOT com>, pgcc AT delorie DOT com
References:	<m13FaNw-0001zHC AT chkw386 DOT ch DOT pwr DOT wroc DOT pl>
Mime-Version:	1.0
User-Agent:	Mutt/1.2.1i
In-Reply-To:	<m13FaNw-0001zHC@chkw386.ch.pwr.wroc.pl>; from strasbur@chkw386.ch.pwr.wroc.pl on Fri, Jul 21, 2000 at 10:50:28AM +0000
X-Operating-System:	Linux version 2.2.16 (root AT cerebro) (gcc driver version pgcc-2.95.2 19991024 (release) executing gcc version 2.7.2.3)
Reply-To:	pgcc AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	pgcc AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Fri, Jul 21, 2000 at 10:50:28AM +0000, Krzysztof Strasburger <strasbur AT chkw386 DOT ch DOT pwr DOT wroc DOT pl> wrote:
> >message after lilo with most of the dots, then the machine reboots.
> Pgcc probably inserts P6 instructions into the code, even if it should not
> do it.

It should ;) When you configure pgcc for i686 when compiling it, it will
of course compile startup-objects and libgcc with p6 optimizations. It
will then be able to compile p5-only programs, but you will not be able to
link them ;)

If you ./configure i585-pc-linux-gnu for example, it will happily generate
pentium-code (as a matter of fact my answering machine is a 486 and pgcc
compiles code for it just fine).

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

- Raw text -