From: Tulio Magno Quites Machado Filho <tuliom@ascii.art.br>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>,
Siddhesh Poyarekar <siddhesh@sourceware.org>,
libc-alpha@sourceware.org
Cc: fweimer@redhat.com
Subject: Re: [PATCH v2 1/2] Move __isnanf128 to libc.so
Date: Mon, 29 Mar 2021 19:02:59 -0300 [thread overview]
Message-ID: <87lfa51uuk.fsf@linux.ibm.com> (raw)
In-Reply-To: <23ecfc94-2588-9c9b-6171-1565739c0c8b@gotplt.org>
Siddhesh Poyarekar <siddhesh@gotplt.org> writes:
> Tulio, could you please take a look at this, specifically the macro soup
> I've come up with for ppc64le to get the symbols in the right places?
They seem alright. LGTM.
I had to solve a few minor conflicts.
I pushed the patch I tested to
https://github.com/tuliom/glibc/commit/cb3b6053b60dce5c5aee11bc2cc528f8e9551e06
--
Tulio Magno
next prev parent reply other threads:[~2021-03-29 22:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 10:19 [PATCH 0/2] math symbols cleanup Siddhesh Poyarekar
2021-02-11 10:19 ` [PATCH 1/2] Move __isnanf128 to libc.so Siddhesh Poyarekar
2021-02-11 10:27 ` Florian Weimer
2021-02-11 14:14 ` [PATCH v2 " Siddhesh Poyarekar
2021-02-11 16:03 ` Florian Weimer
2021-03-29 13:57 ` Siddhesh Poyarekar
2021-03-29 22:02 ` Tulio Magno Quites Machado Filho [this message]
2021-03-30 9:31 ` [COMMITTED] " Siddhesh Poyarekar
2021-02-11 10:19 ` [PATCH 2/2] Avoid adding duplicated symbols into static libraries Siddhesh Poyarekar
2021-03-30 19:47 ` Adhemerval Zanella
2021-03-31 2:57 ` Siddhesh Poyarekar
2021-03-31 13:54 ` Tulio Magno Quites Machado Filho
2021-03-31 14:05 ` Siddhesh Poyarekar
2021-03-02 6:09 ` [PING][PATCH 0/2] math symbols cleanup Siddhesh Poyarekar
2021-03-22 4:36 ` Siddhesh Poyarekar
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=87lfa51uuk.fsf@linux.ibm.com \
--to=tuliom@ascii.art.br \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@gotplt.org \
--cc=siddhesh@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).