https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53679
Ian Lance Taylor changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53679
--- Comment #6 from Mike Frysinger 2013-01-26
03:20:51 UTC ---
Ian has pushed the patch to trunk:
http://gcc.gnu.org/viewcvs?view=revision&revision=195482
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53679
--- Comment #5 from Mike Frysinger 2012-12-23
23:32:35 UTC ---
posted a patch here to add --disable-werror:
http://gcc.gnu.org/ml/gcc-patches/2012-12/msg01379.html
we need this for ChromiumOS ...
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53679
Mike Frysinger changed:
What|Removed |Added
CC||toolchain at gentoo dot org
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53679
--- Comment #3 from Allan McRae 2012-06-15
22:36:54 UTC ---
Just to be clear, I have not modified the compiler to enable fortify by
default, but it is in my CFLAGS...
As this is the only place that glibc's decision to enforce a check on the
retu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53679
--- Comment #2 from Andrew Pinski 2012-06-15
16:41:53 UTC ---
Actually this is due to your modifications to gcc to enable fority by default
and glibc's bad idea that write needs to be check for error after each write.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53679
safety0ff.bugz at gmail dot com changed:
What|Removed |Added
Attachment #27626|Allows me to compile it, I |Allows me to compile it,
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53679
--- Comment #1 from safety0ff.bugz at gmail dot com 2012-06-15 15:52:18 UTC ---
Created attachment 27626
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27626
Allows me to compile it, I do know if there's any value if checking for errors
writin
