public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "elizabeth dot l dot yip at boeing dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/31197] [4.3/4.2 regression^2] TRANSPOSE/RESHAPE and strings Date: Tue, 15 May 2007 06:48:00 -0000 [thread overview] Message-ID: <20070515064800.11371.qmail@sourceware.org> (raw) In-Reply-To: <bug-31197-6642@http.gcc.gnu.org/bugzilla/> ------- Comment #10 from elizabeth dot l dot yip at boeing dot com 2007-05-15 07:48 ------- The following code exposes the problem relating to conjg(transpose(.)), with which gfortran returns the wrong answer. If we break conjg(transpose(.)) into two lines, then we can get the right answer. Is this related to bugs 31196, 31197 and 31258? Should I resubmit this as a new bug? I have tried versions 4.1, 4.2 and the latest 4.3 (05-14-07). I could'nt find a version that works. Elizabeth Yip --------------------------------------------------------------------- program main implicit none complex (kind=4),dimension(2,2)::a,b,c a(1,1) = (1.,1.) a(2,1) = (2.,2.) a(1,2) = (3.,3.) a(2,2) = (4.,4.) print *,"original",a b=conjg(transpose(a)) print *,"H(a)-wrong",b c=transpose(a) c=conjg(c) print *,"H(a)-right",c END program main -- elizabeth dot l dot yip at boeing dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |elizabeth dot l dot yip at | |boeing dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31197
next prev parent reply other threads:[~2007-05-15 6:48 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-03-16 11:26 [Bug fortran/31197] New: wrong code generated with gfortran jv244 at cam dot ac dot uk 2007-03-16 13:25 ` [Bug fortran/31197] wrong code generated with TRANSPOSE/RESHAPE and strings burnus at gcc dot gnu dot org 2007-04-18 9:54 ` [Bug fortran/31197] [4.3/4.2 regression^2] " fxcoudert at gcc dot gnu dot org 2007-04-18 14:56 ` tobi at gcc dot gnu dot org 2007-04-18 18:30 ` tobi at gcc dot gnu dot org 2007-05-04 16:21 ` jvdelisle at gcc dot gnu dot org 2007-05-04 16:29 ` fxcoudert at gcc dot gnu dot org 2007-05-04 16:51 ` jvdelisle at gcc dot gnu dot org 2007-05-04 19:39 ` jvdelisle at gcc dot gnu dot org 2007-05-04 21:29 ` burnus at gcc dot gnu dot org 2007-05-15 6:48 ` elizabeth dot l dot yip at boeing dot com [this message] 2007-05-21 19:10 ` elizabeth dot l dot yip at boeing dot com 2007-06-11 12:53 ` pault at gcc dot gnu dot org 2007-06-30 9:16 ` [Bug fortran/31197] [4.2/4.4 regression] " pinskia at gcc dot gnu dot org 2007-07-03 18:33 ` [Bug fortran/31197] [4.2/4.3 " jv244 at cam dot ac dot uk 2007-07-03 18:36 ` tobi at gcc dot gnu dot org 2007-07-04 3:06 ` mmitchel at gcc dot gnu dot org 2007-07-04 8:50 ` pault at gcc dot gnu dot org 2007-07-04 9:09 ` jv244 at cam dot ac dot uk 2007-07-04 9:10 ` jv244 at cam dot ac dot uk 2007-07-04 9:27 ` pault at gcc dot gnu dot org 2007-07-04 10:05 ` jv244 at cam dot ac dot uk 2007-07-04 10:51 ` Tobias dot Schlueter at physik dot uni-muenchen dot de 2007-07-04 11:32 ` pault at gcc dot gnu dot org 2007-08-30 22:11 ` pault at gcc dot gnu dot org 2007-08-30 22:13 ` pault 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=20070515064800.11371.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: linkBe 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).