public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/32140] [4.3 Regression] Miscompilation with -O1 Date: Wed, 20 Jun 2007 14:08:00 -0000 [thread overview] Message-ID: <20070620140800.11971.qmail@sourceware.org> (raw) In-Reply-To: <bug-32140-6642@http.gcc.gnu.org/bugzilla/> ------- Comment #27 from rguenther at suse dot de 2007-06-20 14:07 ------- Subject: Re: [4.3 Regression] Miscompilation with -O1 On Wed, 20 Jun 2007, jv244 at cam dot ac dot uk wrote: > > > ------- Comment #24 from jv244 at cam dot ac dot uk 2007-06-20 14:03 ------- > (In reply to comment #22) > > It would be nice if a fortraner could make the testcase not output to > > stdout/err > > but to /dev/null instead. > > > > open(6,'/dev/null') > > > > didn't work for me ;) > > > > Just to make a testcase suitable for the testsuite. > > The following testcase, for an unpatched compiler, aborts at -O1, works fine at > -O0, and doesn't write to stdout/stderr... I guess that fits the testsuite ? Yep, I'll use that. Thanks, Richard. > MODULE TEST > CONTAINS > PURE FUNCTION s2a_3(s1,s2,s3) RESULT(a) > CHARACTER(LEN=*), INTENT(IN) :: s1, s2, s3 > CHARACTER(LEN=4), DIMENSION(3) :: a > > a(1)=s1; a(2)=s2; a(3)=s3 > END FUNCTION > END MODULE > > USE TEST > character(len=12) :: line > write(line,'(3A4)') s2a_3("a","bb","ccc") > IF (line.NE."a bb ccc") CALL ABORT() > END > > > -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32140
next prev parent reply other threads:[~2007-06-20 14:08 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-05-29 15:03 [Bug fortran/32140] New: wrong code jv244 at cam dot ac dot uk 2007-05-29 15:32 ` [Bug fortran/32140] [4.3 Regression] Miscompilation with -O1 burnus at gcc dot gnu dot org 2007-05-29 15:41 ` jv244 at cam dot ac dot uk 2007-05-29 18:09 ` [Bug middle-end/32140] " burnus at gcc dot gnu dot org 2007-05-29 18:15 ` burnus at gcc dot gnu dot org 2007-05-29 18:26 ` pinskia at gcc dot gnu dot org 2007-05-30 9:23 ` jv244 at cam dot ac dot uk 2007-06-03 9:02 ` jv244 at cam dot ac dot uk 2007-06-12 15:47 ` [Bug fortran/32140] " fxcoudert at gcc dot gnu dot org 2007-06-13 0:55 ` jvdelisle at gcc dot gnu dot org 2007-06-15 14:43 ` jv244 at cam dot ac dot uk 2007-06-15 15:12 ` fxcoudert at gcc dot gnu dot org 2007-06-15 15:22 ` pinskia at gmail dot com 2007-06-16 19:04 ` jv244 at cam dot ac dot uk 2007-06-17 17:54 ` pault at gcc dot gnu dot org 2007-06-17 21:40 ` [Bug middle-end/32140] " pinskia at gcc dot gnu dot org 2007-06-17 21:45 ` [Bug fortran/32140] " pinskia at gcc dot gnu dot org 2007-06-17 22:08 ` pinskia at gcc dot gnu dot org 2007-06-18 1:49 ` jvdelisle at gcc dot gnu dot org 2007-06-20 8:48 ` jv244 at cam dot ac dot uk 2007-06-20 8:52 ` fxcoudert at gcc dot gnu dot org 2007-06-20 13:22 ` pinskia at gmail dot com 2007-06-20 13:53 ` rguenth at gcc dot gnu dot org 2007-06-20 13:55 ` rguenth at gcc dot gnu dot org 2007-06-20 14:03 ` pinskia at gcc dot gnu dot org 2007-06-20 14:03 ` jv244 at cam dot ac dot uk 2007-06-20 14:05 ` pinskia at gcc dot gnu dot org 2007-06-20 14:08 ` rguenther at suse dot de [this message] 2007-06-20 14:57 ` rguenth at gcc dot gnu dot org 2007-06-20 14:59 ` rguenth 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=20070620140800.11971.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).