public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/67567] resolve.c: gfc_error called with iface->module == NULL
Date: Sat, 26 Sep 2015 18:04:00 -0000	[thread overview]
Message-ID: <bug-67567-4-kqJGs69h0N@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67567-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67567

Paul Thomas <pault at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #8 from Paul Thomas <pault at gcc dot gnu.org> ---
Dear Manuel,

It has been fixed. I would be grateful if you did not put comments like that in
the source code. The PR is quite sufficient!

Thanks for getting to the cause of this problem. Ultimately, it was due to a
change in the way that submodule files are named and was missed because the
testcase does not check the complete messages.

Cheers y muchas gracias!

Paul


  parent reply	other threads:[~2015-09-26 18:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14  6:11 [Bug fortran/67567] New: pretty-print.h sanitizer detects NULL pointer passed to obstack_grow zeccav at gmail dot com
2015-09-14 10:14 ` [Bug fortran/67567] resolve.c: gfc_error called with iface->module == NULL manu at gcc dot gnu.org
2015-09-14 14:27 ` zeccav at gmail dot com
2015-09-14 16:24 ` manu at gcc dot gnu.org
2015-09-25 14:24 ` manu at gcc dot gnu.org
2015-09-26 18:04 ` pault at gcc dot gnu.org [this message]
2015-09-26 18:11 ` paul.richard.thomas at gmail dot com

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=bug-67567-4-kqJGs69h0N@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --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).