From: JonY <10walls@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] gcc: Make strchr return value pointers const
Date: Fri, 4 Sep 2020 09:21:54 +0000 [thread overview]
Message-ID: <bea928e2-0518-c6cd-7fe6-99eab47e9231@gmail.com> (raw)
In-Reply-To: <20200901130142.6366-1-martin@martin.st>
[-- Attachment #1.1: Type: text/plain, Size: 385 bytes --]
On 9/1/20 1:01 PM, Martin Storsjö wrote:
> This fixes compilation of codepaths for dos-like filesystems
> with Clang. When built with clang, it treats C input files as C++
> when the compiler driver is invoked in C++ mode, triggering errors
> when the return value of strchr() on a pointer to const is assigned
> to a pointer to non-const variable.
>
Ping any reviewers?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-09-04 9:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 13:01 Martin Storsjö
2020-09-04 9:21 ` JonY [this message]
2020-09-04 9:32 ` Jakub Jelinek
2020-09-04 12:47 ` Martin Storsjö
2020-09-08 0:13 ` JonY
2020-09-08 11:16 ` Richard Sandiford
2020-09-08 11:50 ` Jakub Jelinek
2020-09-08 12:03 ` Martin Storsjö
2020-09-17 3:56 ` Jeff Law
2020-09-17 6:19 ` JonY
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=bea928e2-0518-c6cd-7fe6-99eab47e9231@gmail.com \
--to=10walls@gmail.com \
--cc=gcc-patches@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).