🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: gnu.gcc.help
Article #42002

Re: Upgrading from 2.7.0 -> 2.7.2

#42002
From: Zachary R Amsden
Date: Fri, 26 Jan 1996 00:00
23 lines
1455 bytes
I believe the problem is that you are trying to compile without
optimization.  Use the -O2 flag, with -fno-strength-reduce as well to avoid
the SR bug, in the kernel base Makefile.  Inconsistent operand constraints
can occur if one of the following conditions holds:

1) Inline assembly code references memory operands that gcc will copy into
machine registers.  You can avoid this with -fforce-mem

2) Code produces a tree of subexpressions which gcc attempts to optimize in
more than one way.  This sometimes happens if both -fforce-mem and
-fforce-addr are enabled together.

3) Code contains inline function references, and -finline-functions is
required to compile properly, but missing

Safest is probably just -O2 -fno-strength-reduce -fomit-frame-pointer
(Linux kernel, right?)

The technical details of the compiler optimization here might not be exactly
right, and may vary between gcc versions, but the way to fix it should work. 

Zach R. Amsden
amsden+@andrew.cmu.edu
Technical Details
Message-ID: <Ul2DplW00WBMA3065O@andrew.cmu.edu>
Path: arc1-ca.pugleaf.net!unknown!not-for-mail
References: <DLsI7s.CBH@physics.purdue.edu>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 11318c,5358e50e8e2d5a90
X-Google-Attributes: gid11318c,public
From: Zachary R Amsden <amsden+@andrew.cmu.edu>
Subject: Re: Upgrading from 2.7.0 -> 2.7.2
Date: 1996/01/26
Message-ID: <Ul2DplW00WBMA3065O@andrew.cmu.edu>
X-Deja-AN: 136697131
references: <DLsI7s.CBH@physics.purdue.edu>
organization: Freshman, Computer Science, Carnegie Mellon, Pittsburgh, PA
newsgroups: gnu.gcc.help