public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/56867] Missing temporary with string array assignment
Date: Mon, 08 Apr 2013 12:17:00 -0000 [thread overview]
Message-ID: <bug-56867-4-ULsv6kiJjd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56867-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56867
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
--- Comment #5 from Tobias Burnus <burnus at gcc dot gnu.org> 2013-04-08 12:17:16 UTC ---
gfortran seems to be in good company. I get
23cd
2334
33yz <<<
using gfortran 4.1, 4.3, 4.4, 4.5, 4.6, 4.7, 4.8, 4.9. But also using NAG,
pathf95 and pgf95.
While g95, sunf95, crayftn and ifort have the correct result:
23cd
2334
23yz <<<
The issue (or at least the fix) could be related to PR47674, where also no
temporary is generated for a substring. (That code could be handled without
temporary, but using a temporary is probably the simplest. In any case, alias
analysis fails as well.)
next prev parent reply other threads:[~2013-04-08 12:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-07 18:12 [Bug fortran/56867] New: " tkoenig at gcc dot gnu.org
2013-04-07 20:11 ` [Bug fortran/56867] " tkoenig at gcc dot gnu.org
2013-04-07 20:15 ` burnus at gcc dot gnu.org
2013-04-07 20:19 ` tkoenig at gcc dot gnu.org
2013-04-07 20:39 ` dominiq at lps dot ens.fr
2013-04-08 12:17 ` burnus at gcc dot gnu.org [this message]
2013-04-08 20:24 ` tkoenig at gcc dot gnu.org
2014-12-28 12:03 ` tkoenig at gcc dot gnu.org
2014-12-28 12:36 ` tkoenig at gcc dot gnu.org
2015-01-07 22:32 ` tkoenig at gcc dot gnu.org
2015-01-24 21:30 ` tkoenig at gcc dot gnu.org
2015-01-24 21:32 ` tkoenig at gcc dot gnu.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=bug-56867-4-ULsv6kiJjd@http.gcc.gnu.org/bugzilla/ \
--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).