public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl dot washington dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/19926] Incorrect rank with PARAMETER and array element.
Date: Sat, 11 Jun 2005 13:49:00 -0000 [thread overview]
Message-ID: <20050611134904.6393.qmail@sourceware.org> (raw)
In-Reply-To: <20050212162405.19926.sgk@troutmask.apl.washington.edu>
------- Additional Comments From sgk at troutmask dot apl dot washington dot edu 2005-06-11 13:49 -------
Subject: Re: Incorrect rank with PARAMETER and array element.
On Sat, Jun 11, 2005 at 09:39:13AM -0000, eedelman at acclab dot helsinki dot fi wrote:
>
> Just to elaborate on what I meant with suspecting thet the patch only hides the
> problem instead of solving it.
>
> One thing that slightly worries my is, why isn't e->rank zero by itself?
You might be right that this is papering over the true bug.
The code looks like
case FL_PARAMETER:
if (sym->value && sym->value->expr_type != EXPR_ARRAY)
{
e = gfc_copy_expr (sym->value);
e->rank = 0;
}
e = gfc_copy_expr (sym->value) literally copies the sym->value expression
node into the e expression node. sym->value->rank is 1. We've probably
kludged around the bug by setting e->rank = 0. So, how do we get here.
sym->value->expr_type == EXPR_CONSTANT because of PARAMETER in "REAL,
PARAMETER :: map(0:50) = 0". I'll look at this sometime today.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19926
next prev parent reply other threads:[~2005-06-11 13:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-12 21:10 [Bug fortran/19926] New: " sgk at troutmask dot apl dot washington dot edu
2005-02-12 21:35 ` [Bug fortran/19926] " pinskia at gcc dot gnu dot org
2005-03-12 12:57 ` toon at moene dot indiv dot nluug dot nl
2005-06-10 23:35 ` eedelman at acclab dot helsinki dot fi
2005-06-11 9:39 ` eedelman at acclab dot helsinki dot fi
2005-06-11 12:44 ` eedelman at acclab dot helsinki dot fi
2005-06-11 13:49 ` sgk at troutmask dot apl dot washington dot edu [this message]
2005-06-13 1:49 ` kargl at gcc dot gnu dot org
2005-06-18 18:16 ` cvs-commit at gcc dot gnu dot org
2005-06-18 18:21 ` [Bug fortran/19926] [4.0 only] " kargl at gcc dot gnu dot org
2005-06-18 18:27 ` cvs-commit at gcc dot gnu dot org
2005-07-08 21:21 ` cvs-commit at gcc dot gnu dot org
2005-07-08 21:25 ` cvs-commit at gcc dot gnu dot org
2005-07-08 21:26 ` kargl 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=20050611134904.6393.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).