On Fri, 2005-09-16 at 00:37 -0500, Joe Wreschnig wrote: > On Thu, 2005-09-15 at 19:47 -0700, Steve Langasek wrote: > > If you have a patch that fixes the ICEs on m68k, by all means please forward > > it to the BTS. > > > > But a larger question is, why are so many packages being built entirely with > > -O3 when policy recommends -O2? Policy does say it's ok to use other > > compiler flags if appropriate, but I'd be surprised if all of these packages > > have been benchmarked to confirm that -O3 actually gives measurable > > performance benefits. > > I don't know if it gives measurable benefits, but all Python extensions > use -O3 by default (from /usr/lib/python2.3/config/Makefile). Personally > I think it's dumb, but maybe the Python maintainers know better? This is > what triggered the bug in python-flac for me. Overriding distutils isn't > something I've figured out yet (doing so is a task for the weekend). I guess I should ask here, too. Does anyone know why Python is compiled with -O3 rather than -O2? Also, does anyone know the best way to override distutils on a per-arch basis to change that? -- Joe Wreschnig <piman@debian.org>
Attachment:
signature.asc
Description: This is a digitally signed message part