public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: sysmaint@contek.com (Douglas Wells)
To: gcc-bugs@gcc.gnu.org
Subject: Re: [Bug fortran/32801] USE of ISO_C_BINDING, ONLY: C_LOC  causes compiler seg fault
Date: Thu, 09 Aug 2007 00:50:00 -0000	[thread overview]
Message-ID: <20070809005020.7DB7D3C39B@mail.contek.com> (raw)
In-Reply-To: <20070806092010.29220.qmail@sourceware.org>


> 
> 
> ------- 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


       reply	other threads:[~2007-08-09  0:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070806092010.29220.qmail@sourceware.org>
2007-08-09  0:50 ` Douglas Wells [this message]
2007-07-17 23:58 [Bug fortran/32801] New: " sysmaint at contek dot com
2007-07-18  5:44 ` [Bug fortran/32801] " burnus at gcc dot gnu dot org
2007-07-18 11:24 ` fxcoudert at gcc dot gnu dot org
2007-07-18 20:19 ` crickett at lanl dot gov
2007-07-18 21:15 ` patchapp at dberlin dot org
2007-07-18 22:02 ` burnus at gcc dot gnu dot org
2007-07-18 22:06 ` burnus at gcc dot gnu dot org
2007-07-21 20:31 ` kargl at gcc dot gnu dot org
2007-07-21 20:41 ` kargl at gcc dot gnu dot org
2007-08-06  9:20 ` fxcoudert at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070809005020.7DB7D3C39B@mail.contek.com \
    --to=sysmaint@contek.com \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).