public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dev-zero at gentoo dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/95889] corrupt size vs. prev_size and hang when using __has_include with -traditional-cpp
Date: Thu, 25 Jun 2020 07:22:26 +0000 [thread overview]
Message-ID: <bug-95889-4-vPsacq2LFk@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
--- Comment #1 from Tiziano Müller <dev-zero at gentoo dot org> ---
Unfortunately `__has_include` is even being parsed (in traditional-cpp mode) if
enclosed in a `if 0 ... endif`:
****snip****
#if 0
#if __has_include(<foo.h>)
#endif
#endif
****snip****
which gives:
****snip****
# 32 "<command-line>" 2
# 1 "test2.h"
test2.h:3: error: missing '(' before "__has_include" operand
3 | #if __has_include(<foo.h>)
|
test2.h:3: error: operator "__has_include" requires a header-name
*** Error in
`/data/tiziano/cp2k/tools/toolchain/install/gcc-10.1.0/lib/gcc/x86_64-pc-linux-gnu/10.1.0/cc1':
corrupted size vs. prev_size: 0x000000000249a7e0 ***
test2.h:1: confused by earlier errors, bailing out
****snip****
while enclosing it in parenthesis at least fixes that, such that the following
parses fine:
****snip****
#if 0
#if (__has_include(<foo.h>))
#endif
#endif
****snip****
next prev parent reply other threads:[~2020-06-25 7:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 7:06 [Bug preprocessor/95889] New: " dev-zero at gentoo dot org
2020-06-25 7:22 ` dev-zero at gentoo dot org [this message]
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 ` [Bug preprocessor/95889] [10 regression] __has_include broken with -traditional-cpp (and therefore with Fortran) tm@dev-zero.ch
2020-07-29 12:53 ` 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-vPsacq2LFk@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).