The almighty cflags

Today was forced to close the Nth bug filled by someone that didn’t know what he was doing with the cflags. That was a waste of time of about 10minutes for 3 developers that actually had a look at the bug, another item that got in the mailbox of many other developers and another line in the bugzilla db.

I have nothing against try to get some performance from some experimental gcc optimization, you are free to do whatever you want on your system, but PLEASE, before filling a bug about missing registers while building something on x86 or amd64, turn OFF all your experimental stuff and just use -O2 -march=${yourcpu} -fomit-frame-pointer -pipe.

Thanks for the understanding.

One thought on “The almighty cflags”

  1. Hi Luca,
    you are about the 10th person on planet gentoo who complains about this problems.
    I had just a little idea, why don’t you change the emerge script, so that it prints a little message when it notices that an emerge did fail and the person is using insane cflags.
    “This error/bug could be a consequence of your insane cflags. Please try to recompile with “-O2 …” and dont fill a bug report before.”

    I don’t think this should be too difficult to implement and I think at least some of these people would listen to it.


Leave a Reply

Your email address will not be published.