public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikael at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/38062] FAIL: gfortran.dg/include_2.f90 -O (test for excess errors): error: stray '#' in program
Date: Tue, 09 Dec 2008 00:51:00 -0000 [thread overview]
Message-ID: <20081209005007.22233.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38062-276@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from mikael at gcc dot gnu dot org 2008-12-09 00:50 -------
(In reply to comment #2)
> The test didn't fail in my last build on head. Was there a recent backport
> that might have fixed this PR?
Not really, I was having a look at forgotten PRs
>
> > If so, can you provide more information (host, version, configure options)?
>
> ../gcc/configure --with-gnu-as --with-as=/usr/local/bin/as --enable-shared
> --prefix=/opt/gnu/gcc/gcc-4.3.2 --with-gmp=/opt/gnu/gcc/gcc-4.3.2
> --enable-debug=no --disable-nls --enable-checking=release
> --enable-languages="c,c++,objc,fortran,ada,obj-c++"
>
> The rest of the info is already in the PR (host, target, build).
Yes, sorry.
>
> Is there a way to capture the generated .c file?
I'm not sure there should be a .c generated file here.
Can you compile the file with your host fortran compiler? With the bootstrapped
f951?
(For me, both work with the -g3 option)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38062
next prev parent reply other threads:[~2008-12-09 0:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 22:33 [Bug target/38062] New: " danglin at gcc dot gnu dot org
2008-12-08 22:53 ` [Bug target/38062] " mikael at gcc dot gnu dot org
2008-12-08 23:19 ` dave at hiauly1 dot hia dot nrc dot ca
2008-12-09 0:51 ` mikael at gcc dot gnu dot org [this message]
2008-12-13 17:48 ` dave at hiauly1 dot hia dot nrc dot ca
2008-12-13 17:53 ` danglin at gcc dot gnu dot org
2008-12-14 22:33 ` danglin at gcc dot gnu dot org
2008-12-14 22:34 ` danglin 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=20081209005007.22233.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: 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).