On Feb 18, 2008 11:40 AM, walter harms <[EMAIL PROTECTED]> wrote: > hi list, > the point of my patch, is that > -Os == Optimise for Size and -g == add debug information > does not make sense.
you mean on the final product, it does not. but while developping the product, yes it does. you can always strip out the debug symbols at a later stage. > > When your compiler creates broken code with -Ox that you should > change the compiler but no debugger can be expected to make sense from code > that > is changed from the original c-source (except asm-level, what does not need > -g). is it your compiler or your debugger that is broken ? could you tell us more about the real problem you faced ? > > And of cause you need to compile twice or do you ship your code with debug > enabled ? of cause not. > But then you can add -O2 or -Os or what ever. no, you do not need to compile twice. from my point of view, this is the flow: source => gcc -Os -g => run => debug (if fix, restart flow) => strip --strip-debug => ship product/soft > > With the current Makefile.flags we enable -Os *everytime* no matter what. this has been the case almost from the start of busybox, no ? -- Christian -- http://detaolb.sourceforge.net/, a linux distribution for Qemu with Git inside ! _______________________________________________ busybox mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/busybox
