public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paulthomas2 at wanadoo dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/28788] [gfortran: 4.1, 4.2 regression] ICE on valid code
Date: Fri, 25 Aug 2006 13:25:00 -0000 [thread overview]
Message-ID: <20060825132542.12142.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28788-2736@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from paulthomas2 at wanadoo dot fr 2006-08-25 13:25 -------
Subject: Re: [gfortran: 4.1, 4.2 regression] ICE on valid
code
martin,
>------- Comment #7 from martin at mpa-garching dot mpg dot de 2006-08-25 12:57 -------
>Hi Paul,
>
>sorry for the late reply, I was away for a few days.
>I compiled the most recent gcc sources, and there still appears to be some
>bad memory access inside gfortran, which causes the compiler to sometimes
>work fine sometimes, sometimes give incorrect errors, and sometimes segfault :(
>
>I have a testcase where gfortran works fine, but reports a bogus error when I
>add
>"-I." to the command line.
>
>I fear the best way to locate this is to use valgrind or something similar on
>the compiler, and I don't manage to produce a small (single-file) testcase at
>the moment. Any ideas what I could do?
>
>
>
>
Perhaps you can let me have an idea of the kind of code that is doing
this? Is this a continuation of the derived type problem or did it
exist prior to the patch of a week back?
A good starting point is to use gdb on
$yourgccpath/libexec/gcc/i*/4.2.0/f951 ;
Then run "command line"
Best regards
Paul
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28788
next prev parent reply other threads:[~2006-08-25 13:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-21 11:37 [Bug fortran/28788] New: " martin at mpa-garching dot mpg dot de
2006-08-22 5:30 ` [Bug fortran/28788] " pault at gcc dot gnu dot org
2006-08-22 20:02 ` pault at gcc dot gnu dot org
2006-08-23 13:20 ` paul dot richard dot thomas at cea dot fr
2006-08-23 14:51 ` patchapp at dberlin dot org
2006-08-24 4:47 ` pault at gcc dot gnu dot org
2006-08-24 4:54 ` pault at gcc dot gnu dot org
2006-08-25 12:57 ` martin at mpa-garching dot mpg dot de
2006-08-25 13:25 ` paulthomas2 at wanadoo dot fr [this message]
2006-08-25 14:36 ` martin at mpa-garching dot mpg dot de
2006-08-25 14:37 ` martin at mpa-garching dot mpg dot de
2006-08-25 17:09 ` jvdelisle at gcc dot gnu dot org
2006-08-26 9:30 ` paulthomas2 at wanadoo dot fr
2006-08-26 12:15 ` aovb94 at dsl dot pipex dot com
2006-08-26 21:27 ` jvdelisle at gcc dot gnu dot org
2006-08-28 11:57 ` paul dot richard dot thomas at cea dot fr
2006-08-29 4:51 ` pault at gcc dot gnu dot org
2006-08-29 4:57 ` pault at gcc dot gnu dot org
2006-08-30 4:37 ` pault 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=20060825132542.12142.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).