public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "matthijs at stdin dot nl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/80753] __has_include and __has_include_next taints subsequent I/O errors
Date: Wed, 23 Sep 2020 14:24:53 +0000 [thread overview]
Message-ID: <bug-80753-4-nYJAJX4FjW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-80753-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80753
Matthijs Kooijman <matthijs at stdin dot nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |matthijs at stdin dot nl
--- Comment #3 from Matthijs Kooijman <matthijs at stdin dot nl> ---
I also ran into this, this is still a problem in gcc 10.0.1.
This is a particular problem in the Arduino environment, which relies on
preprocessor error messages to automatically pick libraries to include. This
bug prevents it from detecting that a particular library is needed and from
adding it to the include path, breaking the build (that could have worked
without this bug).
next parent reply other threads:[~2020-09-23 14:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-80753-4@http.gcc.gnu.org/bugzilla/>
2020-09-23 14:24 ` matthijs at stdin dot nl [this message]
2020-09-23 16:00 ` matthijs at stdin dot nl
2023-06-12 17:15 ` pinskia at gcc dot gnu.org
2023-06-13 9:35 ` jakub at gcc dot gnu.org
2023-06-15 12:17 ` cvs-commit at gcc dot gnu.org
2023-08-01 10:43 ` jakub 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-80753-4-nYJAJX4FjW@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).