From: Mike Frysinger <vapier@gentoo.org>
To: Andrew Stubbs <ams@codesourcery.com>
Cc: Newlib <newlib@sourceware.org>
Subject: Re: amdgcn build failure
Date: Tue, 22 Mar 2022 21:45:58 -0400 [thread overview]
Message-ID: <Yjp71myp6sSLI6JK@vapier> (raw)
In-Reply-To: <817069b6-873f-54e1-e466-8d4ae827a9ea@codesourcery.com>
[-- Attachment #1: Type: text/plain, Size: 558 bytes --]
On 21 Mar 2022 14:25, Andrew Stubbs wrote:
> On 20/03/2022 01:20, Mike Frysinger wrote:
> > i think you should always use the same name output if you want to override
> > regardless of my recent change. the common code defines this in mlock.c,
> > so i would expect you to put your machine overrides in a mlock.c file in
> > your machine dir.
> >
> > this is how all the setjmp, mem*, and str* funcs all work.
>
> OK, I've confirmed that this patch fixes it.
>
> I don't believe I have the power to commit it myself.
pushed for you
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-03-23 1:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 11:43 Andrew Stubbs
2022-03-20 1:20 ` Mike Frysinger
2022-03-21 14:25 ` Andrew Stubbs
2022-03-23 1:45 ` Mike Frysinger [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=Yjp71myp6sSLI6JK@vapier \
--to=vapier@gentoo.org \
--cc=ams@codesourcery.com \
--cc=newlib@sourceware.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).