Bug 8512

Summary: Compiler flags
Product: [Retired] Red Hat Linux Reporter: Bernhard Rosenkraenzer <bero>
Component: rpmAssignee: Jeff Johnson <jbj>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: gafton
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-02-04 02:19:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Bernhard Rosenkraenzer 2000-01-16 11:28:51 UTC
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-04 02:19:59 UTC
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