[Bug gprof/13325] gprof doesn't work when there are histogram data before the first symbol

2011-10-25 Thread cvs-commit at gcc dot gnu.org
http://sourceware.org/bugzilla/show_bug.cgi?id=13325 --- Comment #4 from cvs-commit at gcc dot gnu.org cvs-commit at gcc dot gnu.org 2011-10-25 08:38:58 UTC --- CVSROOT:/cvs/src Module name:src Changes by:ni...@sourceware.org2011-10-25 08:38:50 Modified files: gprof

[Bug gprof/13325] gprof doesn't work when there are histogram data before the first symbol

2011-10-25 Thread nickc at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=13325 Nick Clifton nickc at redhat dot com changed: What|Removed |Added Status|WAITING |RESOLVED

[Bug binutils/13300] out-of-bounds memcpy in peXXigen.c

2011-10-25 Thread Pascal.Stumpf at cubes dot de
http://sourceware.org/bugzilla/show_bug.cgi?id=13300 --- Comment #3 from Pascal.Stumpf at cubes dot de 2011-10-25 13:47:10 UTC --- Well yeah, of course this will work here (FILNMLEN being used only at those two places). But it's still very prone to break in other places due to the design of those

[Bug binutils/13300] out-of-bounds memcpy in peXXigen.c

2011-10-25 Thread nickc at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=13300 --- Comment #4 from Nick Clifton nickc at redhat dot com 2011-10-25 15:53:29 UTC --- Hi Pascal, Well yeah, of course this will work here (FILNMLEN being used only at those two places). But it's still very prone to break in other places

[Bug ld/13343] New: cannot move location counter backwards - Error message provides useless source-file-name:lineno information

2011-10-25 Thread geza.lore at broadcom dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=13343 Bug #: 13343 Summary: cannot move location counter backwards - Error message provides useless source-file-name:lineno information Product: binutils Version: 2.22

[Bug ld/13343] cannot move location counter backwards - Error message provides useless source-file-name:lineno information

2011-10-25 Thread geza.lore at broadcom dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=13343 Geza Lore geza.lore at broadcom dot com changed: What|Removed |Added Severity|enhancement |minor --

[Bug gprof/13325] gprof doesn't work when there are histogram data before the first symbol

2011-10-25 Thread carrot at google dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=13325 --- Comment #6 from Wei Guozhi carrot at google dot com 2011-10-25 16:34:21 UTC --- (In reply to comment #5) Hi Carrot, You are right - your patch is better. So I have checked it in along with this changelog entry. Cheers Nick

[Bug gprof/13325] gprof doesn't work when there are histogram data before the first symbol

2011-10-25 Thread nickc at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=13325 --- Comment #7 from Nick Clifton nickc at redhat dot com 2011-10-25 16:47:55 UTC --- Hi Carrot, It looks you have checked in your first patch. Doh! Sorry - this should be fixed now. Cheers Nick -- Configure bugmail:

[Bug gprof/13325] gprof doesn't work when there are histogram data before the first symbol

2011-10-25 Thread carrot at google dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=13325 --- Comment #8 from Wei Guozhi carrot at google dot com 2011-10-25 22:02:57 UTC --- (In reply to comment #7) Hi Carrot, It looks you have checked in your first patch. Doh! Sorry - this should be fixed now. I think the comment /*

[Bug gold/13314] ICF clashes with section ordering

2011-10-25 Thread tmsriram at google dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=13314 --- Comment #1 from Sriraman Tallam tmsriram at google dot com 2011-10-26 00:08:16 UTC --- This was pointed out earlier by somebody but it is not really clear to me what the fix must be for this. In the same example, if I have the order :

[Bug gold/13314] ICF clashes with section ordering

2011-10-25 Thread mh-sourceware at glandium dot org
http://sourceware.org/bugzilla/show_bug.cgi?id=13314 --- Comment #2 from Mike Hommey mh-sourceware at glandium dot org 2011-10-26 05:57:06 UTC --- I'm not very much convinced the keep-unique flag would be very practical. Maybe having an option to choose the global behavior of ICF vs. reordering