From: Janus Weil <janus@gcc.gnu.org>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: Paul Richard Thomas <paul.richard.thomas@gmail.com>,
gfortran <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>,
salvatore.filippone@uniroma2.it
Subject: Re: [Patch, Fortran] PR 41714: [OOP] ALLOCATE SOURCE= does not properly copy the value from SOURCE
Date: Sun, 25 Oct 2009 18:05:00 -0000 [thread overview]
Message-ID: <854832d40910251056t331b1babq5e29ee5d1abe0c2f@mail.gmail.com> (raw)
In-Reply-To: <84fc9c000910250813o6eed383cy58dcd0a2df103529@mail.gmail.com>
>>> It looks OK to me except:
>>>
>>>> PR fortran/41714
>>>> * trans-expr.c (gfc_build_memcpy_call): Take care of the case that the
>>>> call to '__builtin_memcpy' is optimized away (replaced by a direct
>>>> assignment).
>>>
>>> How the heck does that work? It comes out as a NOP_EXPR and yet it's
>>> really an assignment..... Is that documented somewhere?
>>
>> That patch looks indeed dubious. It tests for an implementation detail
>> (the memcpy folder returns (void *) ({ *dst = *src; dst; })). You should
>> be able to unconditionally fold-convert to void_type_node as in the
>> original code. Instead tree_annotate_all_with_location should be fixed.
>
> Or rather the FE should not call this function - it assumes that the code
> is already gimplified.
Ok, so you mean one should instead just do the stuff which this
function does, but without the extra checks? Like here:
Index: gcc/fortran/trans.c
===================================================================
--- gcc/fortran/trans.c (Revision 153538)
+++ gcc/fortran/trans.c (Arbeitskopie)
@@ -1282,7 +1282,11 @@ gfc_trans_code (gfc_code * code)
if (res != NULL_TREE && ! IS_EMPTY_STMT (res))
{
if (TREE_CODE (res) == STATEMENT_LIST)
- tree_annotate_all_with_location (&res, input_location);
+ {
+ tree_stmt_iterator i;
+ for (i = tsi_start (res); !tsi_end_p (i); tsi_next (&i))
+ SET_EXPR_LOCATION (tsi_stmt (i), input_location);
+ }
else
SET_EXPR_LOCATION (res, input_location);
Note: Maybe one should rather use 'tree_annotate_one_with_location'
instead of SET_EXPR_LOCATION, but right now this is static in
gimplify.c.
Cheers,
Janus
next prev parent reply other threads:[~2009-10-25 17:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-25 11:49 Janus Weil
2009-10-25 15:11 ` Paul Richard Thomas
2009-10-25 15:13 ` Richard Guenther
2009-10-25 15:45 ` Richard Guenther
2009-10-25 18:05 ` Janus Weil [this message]
2009-10-25 19:00 ` Richard Guenther
2009-10-25 19:12 ` Janus Weil
2009-10-25 21:42 ` Janus Weil
2009-10-25 21:46 ` Janus Weil
2009-10-25 21:58 ` Richard Guenther
2009-10-25 22:10 ` Janus Weil
2009-10-25 22:28 ` Richard Guenther
2009-10-25 23:12 ` Janus Weil
2009-10-26 9:29 ` Janus Weil
2009-10-26 9:31 ` Janus Weil
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=854832d40910251056t331b1babq5e29ee5d1abe0c2f@mail.gmail.com \
--to=janus@gcc.gnu.org \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=paul.richard.thomas@gmail.com \
--cc=richard.guenther@gmail.com \
--cc=salvatore.filippone@uniroma2.it \
/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).