This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug target/32523] disastrous scheduling for POWER5


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32523

--- Comment #11 from Andrew Pinski <pinskia at gcc dot gnu.org> 2010-09-29 22:39:14 UTC ---
(In reply to comment #10)
> which is typically reported as invalid by Pinski right up until it is fixed.  

I just looked into the bugs which you have filed and saw a different pattern. 
I think you are putting too much blame on me.  This is ok as I am the one who
normally touches almost every bug.  In the bugs you filed, I noticed one where
I made a comment which was supposed to be interrupted as an internal developer
comment rather than one about your code.

In another one (PR 30599), the problem was in your code as you were requesting
a truncation to happen; yes we went back and forth on that one but you
requested the truncation and GCC actually did it in that case.  In another it
was about a warning generated because of glibc marking a function to be warned
about.  In another one, GCC did not build because of an older version of Xcode
in Mac OS X.  In another the bug was marked as won't fix in the end but not by
me.

So please be more careful when you saying I close bugs as invalid right until
they are fixed.  Yes it has happened to one bug in the past (though I think I
still say that bug was invalid; I cannot remember the number right now).


Really I should have ignored this trolling really.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]