public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/55568] New: [4.8 regression] FAIL: gfortran.dg/allocate_error_4.f90 -O (test for excess errors) Date: Sun, 02 Dec 2012 20:40:00 -0000 [thread overview] Message-ID: <bug-55568-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55568 Bug #: 55568 Summary: [4.8 regression] FAIL: gfortran.dg/allocate_error_4.f90 -O (test for excess errors) Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: schwab@linux-m68k.org spawn /daten/gcc/gcc-20121201/Build/gcc/testsuite/gfortran1/../../gfortran -B/daten/gcc/gcc-20121201/Build/gcc/testsuite/gfortran1/../../ -B/daten/gcc/gcc-20121201/Build/powerpc64-linux/./libgfortran/ /daten/gcc/gcc-20121201/gcc/testsuite/gfortran.dg/allocate_error_4.f90 -fno-diagnostics-show-caret -O -pedantic-errors -S -m64 -o allocate_error_4.s /daten/gcc/gcc-20121201/gcc/testsuite/gfortran.dg/allocate_error_4.f90:13.12-32: allocate( encode(1,1)%mask(1),encode(1,2)%mask(1)) 1 2 Error: Allocate-object at (1) also appears at (2) /daten/gcc/gcc-20121201/gcc/testsuite/gfortran.dg/allocate_error_4.f90:14.13-31: deallocate( encode(1,1)%mask,encode(1,2)%mask) 1 2 Error: Allocate-object at (1) also appears at (2)
next reply other threads:[~2012-12-02 20:40 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-12-02 20:40 schwab@linux-m68k.org [this message] 2012-12-02 20:40 ` [Bug fortran/55568] " schwab@linux-m68k.org 2012-12-03 1:45 ` hp at gcc dot gnu.org 2012-12-03 1:47 ` hp at gcc dot gnu.org 2012-12-03 7:17 ` dominiq at lps dot ens.fr
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-55568-4@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: 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).