public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/26681] internal compiler error
Date: Wed, 15 Mar 2006 08:14:00 -0000	[thread overview]
Message-ID: <20060315081424.24722.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26681-12360@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from pault at gcc dot gnu dot org  2006-03-15 08:14 -------
Herve,

> So what ? Is there a patch which I should use to correct this error ? Do 
> you need more info to reproduce this ICE ? Please ask and I will try to 
> provide all the available info.
> Thanks.

The could you post the modules sparsem and kinds, please? Your code does not do
very well without them... if you get them to me, I will see if I can identify
the problem

>From the message, you bug appears to be one that I introduced, in a patch for
references to function results from contained results, which has just been
fixed by Jakub Jelenik.

You can download the latest binary from the gfortran wiki. I believe that
Francois-Xavier Coudert rebuilds every night.

I do not believe that pr24558 is anything to do with this because there are no
entry's in your code, unless they are in the modules.

Paul T


-- 


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


  parent reply	other threads:[~2006-03-15  8:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-14 14:39 [Bug fortran/26681] New: " chapuis at tours dot inra dot fr
2006-03-14 14:59 ` [Bug fortran/26681] " pinskia at gcc dot gnu dot org
2006-03-14 15:14 ` Herve dot Chapuis at tours dot inra dot fr
2006-03-14 15:22 ` pinskia at gcc dot gnu dot org
2006-03-14 15:37 ` Herve dot Chapuis at tours dot inra dot fr
2006-03-15  8:14 ` pault at gcc dot gnu dot org [this message]
2006-03-15 16:10 ` 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=20060315081424.24722.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).