From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org, Romain Naour <romain.naour@smile.fr>,
Andreas Larsson <andreas@gaisler.com>
Subject: Re: [PATCH 1/2] Remove 32 bit sparc v7 support
Date: Tue, 26 Nov 2019 15:16:45 -0300 [thread overview]
Message-ID: <ce40fa83-ac5a-a9b3-8ef1-79c3349754f3@linaro.org> (raw)
In-Reply-To: <0266dcfa-f3bf-137b-1eac-c4c67e55e920@linaro.org>
On 13/11/2019 17:34, Adhemerval Zanella wrote:
>
>
> On 13/11/2019 17:32, Joseph Myers wrote:
>> On Wed, 13 Nov 2019, Adhemerval Zanella wrote:
>>
>>> The patch is straighforward:
>>>
>>> - The sparc32 v8 implementations are moved as the generic ones.
>>
>> This needs touching no-longer-generated files to be removed from
>> build-many-glibcs.py just as the previous patch did.
>>
>
> Right, I though I have missed it in some rebase. I will add them again.
>
I will commit this shortly if no one opposes it, I am just finishing
a smoke test on sparcv9 and sparc64.
next prev parent reply other threads:[~2019-11-26 18:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 17:43 [PATCH] Remove 32 bit sparc v8 support Adhemerval Zanella
2019-11-11 18:24 ` Joseph Myers
2019-11-11 19:14 ` Adhemerval Zanella
2019-11-11 22:27 ` Joseph Myers
2019-11-12 12:17 ` [PATCH v2] " Adhemerval Zanella
2019-11-12 13:35 ` Romain Naour
2019-11-12 15:39 ` Andreas Larsson
2019-11-12 20:43 ` Adhemerval Zanella
2019-11-13 19:28 ` [PATCH 1/2] Remove 32 bit sparc v7 support Adhemerval Zanella
2019-11-13 19:28 ` [PATCH 2/2] sparc: Use atomic compiler builtins on sparc Adhemerval Zanella
2019-11-19 14:23 ` Andreas Larsson
2019-11-21 19:43 ` Adhemerval Zanella
2019-11-26 18:16 ` Adhemerval Zanella
2019-11-13 20:32 ` [PATCH 1/2] Remove 32 bit sparc v7 support Joseph Myers
2019-11-13 20:34 ` Adhemerval Zanella
2019-11-26 18:16 ` Adhemerval Zanella [this message]
2019-11-28 17:23 ` Joseph Myers
2019-11-28 17:33 ` Joseph Myers
2019-11-28 19:29 ` Adhemerval Zanella
2019-11-28 20:10 ` Joseph Myers
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ce40fa83-ac5a-a9b3-8ef1-79c3349754f3@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=andreas@gaisler.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=romain.naour@smile.fr \
/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).