public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tobi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/21203] Segfault while compiling libgfortran/intrinsics/selected_int_kind.f90
Date: Sun, 12 Feb 2006 18:47:00 -0000 [thread overview]
Message-ID: <20060212184708.4952.qmail@sourceware.org> (raw)
In-Reply-To: <bug-21203-9565@http.gcc.gnu.org/bugzilla/>
------- Comment #28 from tobi at gcc dot gnu dot org 2006-02-12 18:47 -------
Ralf, this patch should fix the segfault, it shouldn't give you a working
compiler, though.
Index: error.c
===================================================================
--- error.c (revision 110873)
+++ error.c (working copy)
@@ -199,7 +199,7 @@ show_loci (locus * l1, locus * l2)
{
int offset, flag, i, m, c1, c2, cmax;
- if (l1 == NULL)
+ if (!l1 || !l1->lb)
{
error_printf ("<During initialization>\n");
return;
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21203
next parent reply other threads:[~2006-02-12 18:47 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-21203-9565@http.gcc.gnu.org/bugzilla/>
2006-02-12 18:47 ` tobi at gcc dot gnu dot org [this message]
2006-09-25 9:19 ` fxcoudert at gcc dot gnu dot org
2006-10-03 13:10 ` [Bug fortran/21203] gfortran doesn't work on targets/variants without two floating point types fxcoudert at gcc dot gnu dot org
2009-04-14 15:16 ` dfranke at gcc dot gnu dot org
2005-04-25 8:21 [Bug fortran/21203] New: Segfault while compiling libgfortran/intrinsics/selected_int_kind.f90 corsepiu at gcc dot gnu dot org
2005-04-25 13:33 ` [Bug fortran/21203] " pinskia at gcc dot gnu dot org
2005-04-25 14:34 ` corsepiu at gcc dot gnu dot org
2005-04-25 16:38 ` kargl at gcc dot gnu dot org
2005-04-25 17:15 ` corsepiu at gcc dot gnu dot org
2005-05-01 14:44 ` ert at roe dot ac dot uk
2005-05-05 17:25 ` ericw at evcohs dot com
2005-05-11 23:12 ` tobi at gcc dot gnu dot org
2005-05-13 7:56 ` corsepiu at gcc dot gnu dot org
2005-05-13 7:59 ` corsepiu at gcc dot gnu dot org
2005-05-13 18:48 ` kargl at gcc dot gnu dot org
2005-05-13 19:25 ` tobi at gcc dot gnu dot org
2005-05-13 20:34 ` pinskia at gcc dot gnu dot org
2005-05-13 21:30 ` kargl at gcc dot gnu dot org
2005-05-14 6:30 ` corsepiu at gcc dot gnu dot org
2005-05-14 7:00 ` corsepiu at gcc dot gnu dot org
2005-05-14 7:04 ` Andrew Pinski
2005-05-14 7:08 ` Andrew Pinski
2005-05-14 7:04 ` pinskia at physics dot uc dot edu
2005-05-14 7:08 ` pinskia at physics dot uc dot edu
2005-05-14 8:14 ` corsepiu at gcc dot gnu dot org
2005-05-14 8:34 ` corsepiu at gcc dot gnu dot org
2005-05-14 15:25 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
2005-05-14 15:58 ` sgk at troutmask dot apl dot washington dot edu
2005-05-14 16:06 ` sgk at troutmask dot apl dot washington dot edu
2005-05-15 3:55 ` corsepiu at gcc dot gnu dot org
[not found] ` <12687093.1116061034131.JavaMail.root@dtm1eusosrv72.dtm.ops.eu.uu.net>
2005-05-15 18:49 ` Toon Moene
2005-05-15 18:49 ` toon at moene dot indiv dot nluug dot nl
2005-05-16 14:01 ` joel at oarcorp dot com
2005-05-16 14:05 ` corsepiu at gcc dot gnu dot org
2005-05-18 11:24 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
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=20060212184708.4952.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).