public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/31610] [4.3 Regression] ICE with transfer, merge in gfc_conv_expr_descriptor
Date: Sat, 26 Jan 2008 16:23:00 -0000 [thread overview]
Message-ID: <20080126144103.5427.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31610-6528@http.gcc.gnu.org/bugzilla/>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1282 bytes --]
------- Comment #19 from dominiq at lps dot ens dot fr 2008-01-26 14:41 -------
I confirm that the ICEs are gone, however the original test case and the one in
comment #3 ouput garbage: 'A^@^@^@@sÐ@^E^@^@^@^T^@^@^@^U^G^@' for the latter on
i686-apple-darwin9.
Note that g95 gives
In file pr31610.f90:3
string = transfer(merge (transfer(achar (ichar('A')), "x", len(string)), st
1
Warning (148): Not enough data to produce the requested array size in TRANSFER
function at (1)
In file pr31610.f90:3
string = transfer(merge (transfer(achar (ichar('A')), "x", len(string)), st
1
Error: MERGE intrinsic at (1) has different character lengths
for the original test and
In file pr31610_1.f90:1
write(*,*) "'", transfer("A", "x", 20), "'"
1
Warning (148): Not enough data to produce the requested array size in TRANSFER
function at (1)
for the reduced one, the output being
'A^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@'.
I hope this may help to answer the question:
> It points to something being wrong with the scalarization of operators but I am
> blowed if I can see what it is.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31610
next prev parent reply other threads:[~2008-01-26 14:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-17 16:37 [Bug fortran/31610] New: " pinskia at gcc dot gnu dot org
2007-04-18 6:03 ` [Bug fortran/31610] " fxcoudert at gcc dot gnu dot org
2007-04-19 19:47 ` pault at gcc dot gnu dot org
2007-05-28 21:09 ` brooks at gcc dot gnu dot org
2007-05-29 5:59 ` brooks at gcc dot gnu dot org
2007-05-29 6:45 ` patchapp at dberlin dot org
2007-05-29 13:17 ` pault at gcc dot gnu dot org
2007-05-29 13:39 ` pault at gcc dot gnu dot org
2007-05-29 14:05 ` burnus at gcc dot gnu dot org
2007-05-29 14:25 ` dominiq at lps dot ens dot fr
2007-09-17 17:39 ` burnus at gcc dot gnu dot org
2007-11-12 0:19 ` fxcoudert at gcc dot gnu dot org
2007-11-22 9:09 ` fxcoudert at gcc dot gnu dot org
2007-12-08 17:16 ` jvdelisle at gcc dot gnu dot org
2008-01-25 20:23 ` [Bug fortran/31610] [4.3 Regression] " rguenth at gcc dot gnu dot org
2008-01-26 5:12 ` jvdelisle at gcc dot gnu dot org
2008-01-26 5:44 ` jvdelisle at gcc dot gnu dot org
2008-01-26 11:59 ` pault at gcc dot gnu dot org
2008-01-26 16:23 ` dominiq at lps dot ens dot fr [this message]
2008-01-26 17:19 ` jvdelisle at gcc dot gnu dot org
2008-01-26 19:10 ` jvdelisle at gcc dot gnu dot org
2008-01-26 19:14 ` jvdelisle at gcc dot gnu dot org
2008-01-26 19:24 ` [Bug fortran/31610] " jvdelisle at gcc dot gnu dot org
2008-03-15 0:41 ` jsm28 at gcc dot gnu dot org
2008-06-06 14:58 ` rguenth at gcc dot gnu dot org
2008-07-04 19:47 ` jsm28 at gcc dot gnu dot org
2008-11-15 15:21 ` pault at gcc dot gnu dot org
2008-11-15 18:43 ` burnus at gcc dot gnu dot org
2009-01-05 20:10 ` mikael 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=20080126144103.5427.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).