public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/41102] Ease error checking of included files located in the SYSTEM_INCLUDE_DIR/ending in .h
Date: Fri, 30 Oct 2015 17:27:00 -0000 [thread overview]
Message-ID: <bug-41102-4-ROabFlum8G@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-41102-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41102
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #14 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Any point to keep this PR opened? The original issue has been fixed and it's
likely that the include files will be fixed well before any progress will be
made in gfortran.
next prev parent reply other threads:[~2015-10-30 17:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-41102-4@http.gcc.gnu.org/bugzilla/>
2011-11-16 17:04 ` fwi at inducks dot org
2015-10-30 17:27 ` dominiq at lps dot ens.fr [this message]
2015-10-30 17:31 ` dr.i.j.bush at googlemail dot com
2015-10-30 17:41 ` dominiq at lps dot ens.fr
2009-08-18 10:52 [Bug fortran/41102] New: openMP include file causes errors when compiling with standards checking ian dot bush at nag dot co dot uk
2009-08-19 7:14 ` [Bug fortran/41102] Ease error checking of included files located in the SYSTEM_INCLUDE_DIR/ending in .h burnus at gcc dot gnu dot org
2010-05-06 21:40 ` dfranke 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=bug-41102-4-ROabFlum8G@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).