Bug 8512 - Compiler flags
Compiler flags
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: rpm (Show other bugs)
6.1
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnson
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-01-16 06:28 EST by Bernhard Rosenkraenzer
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-02-03 21:19:43 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Bernhard Rosenkraenzer 2000-01-16 06:28:51 EST
Hi, we're still keeping -fno-strength-reduce in rpmrc for i386. It was useful to work around a breakage of gcc versions prior to 2.7.2.2, but doesn't make any sense today. All it does is slow things down.
I can understand it's still in the base package for people who are stuck with old compilers, but we should get rid of it in our rpm rpm. Also, how about adding something along the lines of optflags: i686 -O2 -mpentiumpro -march=i686?
Cc'ing gafton because the same thing is done in the build roots.
Comment 1 Cristian Gafton 2000-02-03 21:19:59 EST
Like it or not, these compiler flags have proven to be safe. We're not about to
change that. And I am sure that we'll not be automatically generating i686
binaries only when rpm is running on a i686

Note You need to log in before you can comment on or make changes to this bug.