public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/18923] segfault after subroutine name confusion
Date: Fri, 18 May 2007 22:53:00 -0000 [thread overview]
Message-ID: <20070518225251.26797.qmail@sourceware.org> (raw)
In-Reply-To: <bug-18923-9515@http.gcc.gnu.org/bugzilla/>
------- Comment #17 from jvdelisle at gcc dot gnu dot org 2007-05-18 23:52 -------
Created an attachment (id=13582)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13582&action=view)
Patch to eliminate segfault
This patch eliminates the segfault from the original test case and the last
test case which happen in to different places. The first test case segfault
was caused by the duplicate else clause. That was sneaky. I was staring at it
quite a while before I noticed it.
--
jvdelisle at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot gnu |jvdelisle at gcc dot gnu dot
|dot org |org
Status|REOPENED |ASSIGNED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18923
next prev parent reply other threads:[~2007-05-18 22:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-18923-9515@http.gcc.gnu.org/bugzilla/>
2006-06-07 3:17 ` jvdelisle at gcc dot gnu dot org
2006-06-07 5:19 ` pinskia at gcc dot gnu dot org
2006-06-29 17:44 ` tobi at gcc dot gnu dot org
2006-07-03 18:35 ` reichelt at gcc dot gnu dot org
2006-10-20 3:26 ` jvdelisle at gcc dot gnu dot org
2007-02-01 20:28 ` reichelt at gcc dot gnu dot org
2007-02-02 2:26 ` jvdelisle at gcc dot gnu dot org
2007-05-18 10:06 ` dfranke at gcc dot gnu dot org
2007-05-18 20:10 ` reichelt at gcc dot gnu dot org
2007-05-18 20:44 ` dfranke at gcc dot gnu dot org
2007-05-18 21:11 ` dfranke at gcc dot gnu dot org
2007-05-18 21:53 ` jvdelisle at gcc dot gnu dot org
2007-05-18 22:53 ` jvdelisle at gcc dot gnu dot org [this message]
2007-05-21 15:25 ` patchapp at dberlin dot org
2007-05-23 4:16 ` jvdelisle at gcc dot gnu dot org
2007-06-02 21:10 ` patchapp at dberlin dot org
2007-06-05 20:24 ` jvdelisle at gcc dot gnu dot org
2007-06-06 1:21 ` jvdelisle at gcc dot gnu dot org
2007-06-06 1:23 ` jvdelisle at gcc dot gnu dot org
2004-12-10 13:00 [Bug fortran/18923] New: " Thomas dot Koenig at online dot de
2004-12-14 22:35 ` [Bug fortran/18923] " tobi at gcc dot gnu dot org
2005-05-22 19:26 ` fxcoudert at gcc dot gnu dot org
2005-06-06 0:42 ` pinskia at gcc dot gnu dot org
2005-06-06 7:59 ` reichelt at gcc dot gnu dot org
2005-06-13 3:28 ` pinskia at gcc dot gnu dot org
2005-07-08 1:44 ` mmitchel at gcc dot gnu dot org
2005-09-18 20:02 ` pinskia 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=20070518225251.26797.qmail@sourceware.org \
--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).