public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at hep dot tu-darmstadt dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/20138] fortran (driver?) bug: array bound checking conflicts with preprocessing
Date: Tue, 22 Feb 2005 15:10:00 -0000 [thread overview]
Message-ID: <20050222084807.19073.qmail@sourceware.org> (raw)
In-Reply-To: <20050222084054.20138.anlauf@hep.tu-darmstadt.de>
------- Additional Comments From anlauf at hep dot tu-darmstadt dot de 2005-02-22 08:48 -------
It looks very much like a driver problem, because the option -std=f95
instead of -C makes it even funnier:
cc1: warning: command line option "-std=f95" is valid for F95 but not for C
But at least it does compile...
-ha
--
What |Removed |Added
----------------------------------------------------------------------------
Summary|fortran (frontend/driver?) |fortran (driver?) bug: array
|bug: array bound checking |bound checking conflicts
|conflicts with preprocessing|with preprocessing
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20138
next prev parent reply other threads:[~2005-02-22 8:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 15:06 [Bug fortran/20138] New: fortran (frontend/driver?) " anlauf at hep dot tu-darmstadt dot de
2005-02-22 15:10 ` anlauf at hep dot tu-darmstadt dot de [this message]
2005-02-22 15:16 ` [Bug fortran/20138] fortran (driver?) " anlauf at hep dot tu-darmstadt dot de
2005-02-22 18:27 ` pinskia at gcc dot gnu dot org
2005-04-10 8:36 ` cvs-commit at gcc dot gnu dot org
2005-04-10 8:44 ` tkoenig 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=20050222084807.19073.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).