public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/62019] [5 Regression] FAIL: gnat.dg/weak2.adb (test for excess errors) on x86_64-apple-darwin13
Date: Sat, 23 Aug 2014 17:00:00 -0000 [thread overview]
Message-ID: <bug-62019-4-35Gg3cCh3N@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62019-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62019
John David Anglin <danglin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |danglin at gcc dot gnu.org
--- Comment #4 from John David Anglin <danglin at gcc dot gnu.org> ---
I see similar error on hppa-unknown-linux-gnu:
/xgcc --GNATBIND=/home/dave/gnu/gcc/objdir/gcc/gnatbind
--GNATLINK=/home/dave/gn
u/gcc/objdir/gcc/gnatlink -cargs -B/home/dave/gnu/gcc/objdir/gcc -largs
--GCC=/home/dave/gnu/gcc/objdir/gcc/xgcc -B/home/dave/gnu/gcc/objdir/gcc
-margs --RTS=/home/dave/gnu/gcc/objdir/hppa-linux-gnu/./libada -q -f
/home/dave/gnu/gcc/gcc/gcc/testsuite/gnat.dg/weak2.adb
-fno-diagnostics-show-caret -fdiagnostics-color=never -c -u -S -o weak2.sraised
STORAGE_ERROR : stack overflow or erroneous memory access
gnatmake: "/home/dave/gnu/gcc/gcc/gcc/testsuite/gnat.dg/weak2.adb" compilation
error
next prev parent reply other threads:[~2014-08-23 17:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 9:23 [Bug ada/62019] New: [4.10 " dominiq at lps dot ens.fr
2014-08-05 9:34 ` [Bug ada/62019] " charlet at gcc dot gnu.org
2014-08-05 12:03 ` ebotcazou at gcc dot gnu.org
2014-08-05 13:02 ` rguenth at gcc dot gnu.org
2014-08-05 19:56 ` dominiq at lps dot ens.fr
2014-08-23 17:00 ` danglin at gcc dot gnu.org [this message]
2014-10-14 21:04 ` [Bug ada/62019] [5 Regression] gnat.dg/weak2.adb fails everywhere ebotcazou at gcc dot gnu.org
2014-10-14 21:07 ` ebotcazou 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-62019-4-35Gg3cCh3N@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).