> > > ------- Comment #8 from fxcoudert at gcc dot gnu dot org 2007-08-06 09:20 > ------- > Without any more news, let's consider this fixed. Douglas, if it so happens > that your bug wasn't fixed by the patch, please reopen this bug-report. > > > -- > > fxcoudert at gcc dot gnu dot org changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|WAITING |RESOLVED > Resolution| |FIXED > > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32801 > > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter.
I apologize for sending this message directly to gcc-bugs, but I feel somewhat powerless. I have replied by e-mail to each of the inquiries that was directed to me to report that this problem has indeed been fixed (at least when I copied the modified files into my source tree and rebuilt). However, none of these replies has made it into the bug-report, I have received no error messages about the replies, and it appears that none of the gcc developers have received my replies. I just tried to update the bug report via the bugzilla web interface, but I didn't see any way to add a comment. When I tried to add an attachment (with the notion that I could omit the attachment), the system complained about the lack of attachment -- and I didn't want to add an empty or useless attachment. Thank you for supporting gfortran. Is there some web page that provides more specific information about how to use bugzilla for gcc? (I'll note that the page http://gcc.gnu.org/bugs.html addresses the issue of what information should goes into the bug report description, not how to operate bugzilla.) Thanks, - dmw
