From: He X <xw897002528@gmail.com>
To: musl@lists.openwall.com, Rich Felker <dalias@libc.org>
Cc: wolf@wolfsden.cz
Subject: Re: [musl] g++ fpermissive compilation error for strdupa
Date: Fri, 24 Jun 2022 13:24:48 +0800 [thread overview]
Message-ID: <CAPG2z0-wDgckMD5FyaEcJma8qkvshuMs2tsu2EhHUdCaLnUSpA@mail.gmail.com> (raw)
In-Reply-To: <YrS+LEo3y9V1gr+x@ws>
> I will explore the possibility of sending a patch to remove this usage
to upstream.
FYI, Wolf, I've opened an issue https://github.com/bazelbuild/bazel/issues/15729
Wolf <wolf@wolfsden.cz> 于2022年6月24日周五 03:25写道：
>
> On 2022-06-23 10:59:07 +0800, He X wrote:
> > > so it's been kinda nice that this is catching bugs in C++ programs.
> >
> > I agreed. I will see what bazel guys say about the usage of strdupa. Maybe
> > they are willing to remove strdupa.
>
> As far as I can tell there is exactly one usage of strdupa in bazel [0].
> And that usage should be fairly easily replaceable by a dynamic
> allocation, or static buffer.
>
> I will explore the possibility of sending a patch to remove this usage
> to upstream.
>
> 0: https://github.com/bazelbuild/bazel/blob/master/src/main/tools/linux-sandbox-pid1.cc#L149
>
> --
> There are only two hard things in Computer Science:
> cache invalidation, naming things and off-by-one errors.
--
Best regards,
xhe
next prev parent reply other threads:[~2022-06-24 5:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 8:05 He X
2022-06-22 13:19 ` Rich Felker
2022-06-23 2:59 ` He X
2022-06-23 3:07 ` Rich Felker
2022-06-23 19:25 ` Wolf
2022-06-24 5:24 ` He X [this message]
2022-06-23 7:40 ` Bartosz Brachaczek
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=CAPG2z0-wDgckMD5FyaEcJma8qkvshuMs2tsu2EhHUdCaLnUSpA@mail.gmail.com \
--to=xw897002528@gmail.com \
--cc=dalias@libc.org \
--cc=musl@lists.openwall.com \
--cc=wolf@wolfsden.cz \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).