public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/110558] __has_include argument expansion results in unexpected filename Date: Mon, 11 Dec 2023 10:44:36 +0000 [thread overview] Message-ID: <bug-110558-4-htGJ0lgSnv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110558-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110558 --- Comment #3 from Florian Weimer <fw at gcc dot gnu.org> --- It tries to read "my. header.h" for some reason, even though the MAKE_INCLUDE_PATH macro produces "my.header.h" in other contexts (not just in #include directives). I doubt this is related to bug 80753.
next prev parent reply other threads:[~2023-12-11 10:44 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-05 11:29 [Bug preprocessor/110558] New: " provisorisch at online dot de 2023-07-05 13:21 ` [Bug preprocessor/110558] " pinskia at gcc dot gnu.org 2023-07-05 14:46 ` provisorisch at online dot de 2023-12-11 10:44 ` fw at gcc dot gnu.org [this message] 2023-12-11 22:06 ` lhyatt at gcc dot gnu.org 2023-12-12 23:20 ` lhyatt at gcc dot gnu.org 2024-03-14 11:33 ` cvs-commit at gcc dot gnu.org 2024-03-14 11:36 ` lhyatt 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-110558-4-htGJ0lgSnv@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: linkBe 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).