public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ivan.lazaric.gcc at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/109988] -iwithprefix doesn't add folder to end of search list Date: Sat, 27 May 2023 00:42:26 +0000 [thread overview] Message-ID: <bug-109988-4-7VUa05n5J3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109988-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109988 --- Comment #3 from Ivan Lazaric <ivan.lazaric.gcc at gmail dot com> --- Note that clang has the same flags and behaves according to the documentation, might be some value in matching it. If it's considered too breaking of a change, I would recommend introducing a -iwithprefixafter flag that would add the directory to the end of the include search list.
prev parent reply other threads:[~2023-05-27 0:42 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-26 12:42 [Bug c++/109988] New: " ivan.lazaric.gcc at gmail dot com 2023-05-26 13:22 ` [Bug c++/109988] " ivan.lazaric.gcc at gmail dot com 2023-05-26 17:42 ` [Bug preprocessor/109988] " pinskia at gcc dot gnu.org 2023-05-27 0:42 ` ivan.lazaric.gcc at gmail dot com [this message]
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-109988-4-7VUa05n5J3@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).