On Fri, Mar 25, 2005 at 04:59:04AM -0800, Steve Langasek wrote:
> On Fri, Mar 25, 2005 at 12:55:59PM +0000, Gerrit Pape wrote:
> > The workaround for sparc wouldn't be necessary if the diet wrapper is
> > called with the -Os option (this adds -mcpu=supersparc), a good idea
> > anyway for all architectures.
> 
> It most certainly is *not* a good idea; it's contraindicated by policy to
> build binaries with -Os instead of -O2, and the idea of calling -Os to set
> -mcpu=supersparc leaves me very much afraid of what other random options
> diet would set.

It's that diet libc is meant to produce statically linked binaries
optimized for size; that's what it's designed for.  Here're the options
it uses on Debian, I'm not aware of any problems they cause.

static const char* Os[] = {
  "i386","-Os","-mpreferred-stack-boundary=2",
         "-malign-functions=1","-malign-jumps=1",
         "-malign-loops=1","-fomit-frame-pointer",0,
  "x86_64","-Os","-fno-omit-frame-pointer",0,
  "sparc","-Os","-mcpu=supersparc",0,
  "sparc64","-Os","-m64","-mhard-quad-float",0,
  "alpha","-Os","-fomit-frame-pointer",0,
  "arm","-Os","-fomit-frame-pointer",0,
  "mips","-Os","-fomit-frame-pointer",0,
  "mipsel","-Os","-fomit-frame-pointer","-mno-abicalls","-fno-pic","-G","0",0,
  "ppc","-Os","-fomit-frame-pointer","-mpowerpc-gpopt","-mpowerpc-gfxopt",0,
  "ppc64","-Os","-fomit-frame-pointer","-mpowerpc-gpopt","-mpowerpc-gfxopt",0,
  "s390","-Os","-fomit-frame-pointer",0,
  "s390x","-Os","-fomit-frame-pointer",0,
  "sh","-Os","-fomit-frame-pointer",0,
  "ia64","-Os",0,
  "x86_64","-Os","-fstrict-aliasing","-momit-leaf-frame-pointer","-mfancy-math-3
87",0,
  0};

Regards, Gerrit.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to