public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave.anglin at bell dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/55884] [4.8 Regression] FAIL: libgomp.fortran/omp_parse3.f90 -O0 (test for excess errors)
Date: Mon, 07 Jan 2013 16:09:00 -0000 [thread overview]
Message-ID: <bug-55884-4-7JnjU38OPh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55884-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55884
--- Comment #4 from dave.anglin at bell dot net 2013-01-07 16:09:14 UTC ---
On 1/7/2013 7:50 AM, jakub at gcc dot gnu.org wrote:
> Guess related to -fintrinsic-module-path.
Have being doing a regression search and it seems to be
pointing to this change. Seem to have to do a full bootstrap
to test. Sometimes test is unresolved.
Will try you your suggestion.
Dave
next prev parent reply other threads:[~2013-01-07 16:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-05 16:30 [Bug driver/55884] New: " danglin at gcc dot gnu.org
2013-01-05 16:37 ` [Bug driver/55884] [4.8 Regression] " danglin at gcc dot gnu.org
2013-01-05 18:59 ` danglin at gcc dot gnu.org
2013-01-07 10:06 ` rguenth at gcc dot gnu.org
2013-01-07 12:51 ` jakub at gcc dot gnu.org
2013-01-07 16:09 ` dave.anglin at bell dot net [this message]
2013-01-08 3:34 ` dave.anglin at bell dot net
2013-01-08 8:13 ` jakub at gcc dot gnu.org
2013-01-08 15:30 ` dave.anglin at bell dot net
2013-01-09 4:16 ` dave.anglin at bell dot net
2013-01-09 4:46 ` dave.anglin at bell dot net
2013-01-13 21:27 ` dave.anglin at bell dot net
2013-01-16 16:20 ` burnus at gcc dot gnu.org
2013-01-16 16:36 ` jakub 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-55884-4-7JnjU38OPh@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).