public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tm@dev-zero.ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/95889] [10 regression] __has_include broken with -traditional-cpp (and therefore with Fortran)
Date: Wed, 29 Jul 2020 08:13:29 +0000 [thread overview]
Message-ID: <bug-95889-4-gmkU0Q67up@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95889-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95889
Tiziano Müller <tm@dev-zero.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|__has_include evaluated |[10 regression]
|even if disabled (with cpp |__has_include broken with
|in traditional-mode) |-traditional-cpp (and
| |therefore with Fortran)
CC| |jakub at gcc dot gnu.org,
| |nathan at acm dot org
--- Comment #4 from Tiziano Müller <tm@dev-zero.ch> ---
Link to patch series here:
https://gcc.gnu.org/pipermail/gcc-patches/2020-July/550832.html
next prev parent reply other threads:[~2020-07-29 8:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 7:06 [Bug preprocessor/95889] New: corrupt size vs. prev_size and hang when using __has_include with -traditional-cpp dev-zero at gentoo dot org
2020-06-25 7:22 ` [Bug preprocessor/95889] " dev-zero at gentoo dot org
2020-07-24 10:34 ` [Bug preprocessor/95889] __has_include evaluated even if disabled (with cpp in traditional-mode) dev-zero at gentoo dot org
2020-07-28 7:56 ` tm@dev-zero.ch
2020-07-29 8:13 ` tm@dev-zero.ch [this message]
2020-07-29 12:53 ` [Bug preprocessor/95889] [10 regression] __has_include broken with -traditional-cpp (and therefore with Fortran) nathan at gcc dot gnu.org
2020-07-29 15:01 ` nathan 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-95889-4-gmkU0Q67up@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).