2 ms·

For an example of a recent bug try this http://gcc.gnu.org/bugzilla//show_bug.cgi?id=56888 http://gcc.gnu.org/bugzilla//show_bug.cgi?id=56888 basically the comp

For an example of a recent bug try this http://gcc.gnu.org/bugzilla//show_bug.cgi?id=56888 http://gcc.gnu.org/bugzilla//show_bug.cgi?id=56888 basically the compiler tries to recognise code that manually does memcpy or memcmp and replaces it with the built in version. Even if you are trying to compile libc where you get an infinite loop when this happens.

jff 13y ago
My colleagues and I often lament how gcc is just so much smarter than all of us. Usually after spending a day figuring out why our code wasn't working, only to discover that gcc was doing something "clever".
- gngeal 13y ago
  This one sounds almost like peephole optimization of sorts. How exactly is that "clever"?
  - duaneb 13y ago
    I assumed it was the ironic sense—it was intended to be clever but just ended up being a bug.
DannyBee 13y ago
It does this for very good reason of course. If you are trying to build a C library, you already have freestanding issues, this is nothing new.
- justincormack 13y ago
  Not sure I follow your comment. This is with -ffreestanding, how are you supposed to compile libc?