https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52544
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52544
Frédéric Leroy changed:
What|Removed |Added
CC||frederic.le...@b-com.com
--- Comment #9
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52544
--- Comment #8 from mobi at mobiphil dot com ---
forgot to mention:
gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
Ubuntu 14.04 LTS _Trusty Tahr_ - Release amd64
Linux 3.16.0-25-lowlatency
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52544
mobi at mobiphil dot com changed:
What|Removed |Added
CC||mobi at mobiphil dot com
--- C
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52544
--- Comment #6 from Rodrigo Campos ---
Actually, I recently find out that the memory corruption thing was not a GCC
bug. It was a really weird error that only appears in the library if you do a
print to stdout (not stderr) before some thing happen
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52544
--- Comment #5 from Rodrigo Campos ---
Ohh, forgot to say, but if I just don't compile with "-finstrument-functions"
the code works as expected. With gcc 4.7, 4.5 and 4.4.
Although, when I compile with gcc 4.5 and 4.4, everything compiles and lin
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52544
Rodrigo Campos changed:
What|Removed |Added
CC||rodrigo at sdfg dot com.ar
--- Comment #
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52544
Richard Guenther changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52544
sebastian changed:
What|Removed |Added
CC||oeste.sebastian at
|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52544
--- Comment #1 from sebastian
2012-07-23 14:47:00 UTC ---
Created attachment 27859
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27859
preprocessed minimal reproduction of the bug
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52544
Andrew Pinski changed:
What|Removed |Added
Component|c |middle-end
Severity|major
11 matches
Mail list logo