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/18022] problem with structure and calling a function
Date: Fri, 08 Jul 2005 09:38:00 -0000 [thread overview]
Message-ID: <20050708093802.20566.qmail@sourceware.org> (raw)
In-Reply-To: <20041015190149.18022.gruel@astro.ufl.edu>
------- Additional Comments From paulthomas2 at wanadoo dot fr 2005-07-08 09:37 -------
(In reply to comment #1)
> This looks like it's a dupe of 15553
> *** This bug has been marked as a duplicate of 15553 ***
This is not correct - 15553 has been resolved.
The present bug comes about because the scalarizer does not recognise that the
lvalues in pts%x = char2real_1d(tab_c(:,1)) are components in an array of
derived types. It instead treats them as an array of reals. This is odd because
rbuffer = char2real_1d(tab_c(:,1))
pts%x = rbuffer
works correctly.
There is something screwed up in gfc_trans_arrayfunc_assign that is causing
this problem. This can be confirmed by rewriting the two assignments as
pts%x = 1.0*char2real_1d(tab_c(:,1))
pts%y = 1.0*char2real_1d(tab_c(:,2)), which now works correctly!!
Thus emboldened, I emliminated the branch to gfc_trans_arrayfunc_assign,
whereupon the bug disappears. What is this function for? The rest of
gfc_trans_assignment does its job correctly.
I will regtest over the weekend and check out whether it is "de-optimising" any
code or not.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18022
next prev parent reply other threads:[~2005-07-08 9:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 19:01 [Bug fortran/18022] New: " gruel at astro dot ufl dot edu
2004-10-21 19:27 ` [Bug fortran/18022] " tobi at gcc dot gnu dot org
2005-07-05 14:52 ` gruel at astro dot ufl dot edu
2005-07-08 9:38 ` paulthomas2 at wanadoo dot fr [this message]
2005-07-08 13:02 ` paulthomas2 at wanadoo dot fr
2005-07-08 13:34 ` gruel at astro dot ufl dot edu
2005-07-09 0:29 ` tobi at gcc dot gnu dot org
2005-07-09 11:39 ` tobi at gcc dot gnu dot org
2005-07-09 11:47 ` tobi at gcc dot gnu dot org
2005-07-09 11:52 ` tobi at gcc dot gnu dot org
2005-07-09 12:04 ` tobi at gcc dot gnu dot org
2005-07-09 12:14 ` tobi at gcc dot gnu dot org
2005-07-09 13:14 ` paulthomas2 at wanadoo dot fr
2005-07-09 14:39 ` paulthomas2 at wanadoo dot fr
2005-07-09 15:12 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
2005-07-09 17:50 ` tobi at gcc dot gnu dot org
2005-07-10 17:22 ` tobi at gcc dot gnu dot org
2005-07-10 17:25 ` paulthomas2 at wanadoo dot fr
2005-07-10 17:37 ` paulthomas2 at wanadoo dot fr
2005-07-10 17:52 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
2005-07-10 18:09 ` paulthomas2 at wanadoo dot fr
2005-08-03 10:01 ` paulthomas2 at wanadoo dot fr
[not found] <bug-18022-9317@http.gcc.gnu.org/bugzilla/>
2005-10-13 4:48 ` pault at gcc dot gnu dot org
2005-10-23 6:59 ` cvs-commit at gcc dot gnu dot org
2005-10-23 15:46 ` cvs-commit at gcc dot gnu dot org
2005-10-23 16:26 ` pault at gcc dot gnu dot org
2005-10-23 22:55 ` 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=20050708093802.20566.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).