public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/58813] SIGSEGV in show_locus at error.c:310
Date: Mon, 21 Oct 2013 16:18:00 -0000	[thread overview]
Message-ID: <bug-58813-4-NlTtwKSgJE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58813-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Mon, Oct 21, 2013 at 04:01:43PM +0000, burnus at gcc dot gnu.org wrote:
> 
> Error: Procedure 'yS???+' in generic interface 't' at (1) is neither
> function nor subroutine
> 
> where the procedure name is garbage.
> 

Like many error messages, this is a run-on error due to the
first one.  If one fixes the first error, the second goes
away.  The best fix would be to change gfc_option.max_errors 
from 25 to 1.


  parent reply	other threads:[~2013-10-21 16:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-20  7:27 [Bug fortran/58813] New: " zeccav at gmail dot com
2013-10-20 17:55 ` [Bug fortran/58813] " kargl at gcc dot gnu.org
2013-10-20 18:40 ` kargl at gcc dot gnu.org
2013-10-21 16:01 ` burnus at gcc dot gnu.org
2013-10-21 16:18 ` sgk at troutmask dot apl.washington.edu [this message]
2013-10-21 17:38 ` zeccav at gmail dot com
2013-10-22 13:08 ` sgk at troutmask dot apl.washington.edu
2013-10-22 17:14 ` zeccav at gmail dot com
2013-11-25  0:58 ` kargl at gcc dot gnu.org
2015-04-10 11:30 ` mikael at gcc dot gnu.org
2015-04-14  9:18 ` mikael at gcc dot gnu.org
2015-04-14 12:24 ` mikael at gcc dot gnu.org
2015-04-14 12:43 ` mikael at gcc dot gnu.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=bug-58813-4-NlTtwKSgJE@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).