From: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
To: Stefan Liebler via Libc-alpha <libc-alpha@sourceware.org>
Cc: Stefan Liebler <stli@linux.ibm.com>
Subject: Re: [PATCH] build-many-glibcs.py: Add some s390x glibc variants.
Date: Wed, 05 Aug 2020 17:39:43 +0200 [thread overview]
Message-ID: <87bljpumo0.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <20200805144511.3482867-1-stli@linux.ibm.com> (Stefan Liebler via Libc-alpha's message of "Wed, 5 Aug 2020 16:45:11 +0200")
* Stefan Liebler via Libc-alpha:
> There is a s390x configure check which checks the architecture level set.
>
> This ALS influences e.g. which ifunc variants are needed or which one is
> the default variant or if the symbol will be an ifunc-symbol at all.
>
> The ALS also enables to use the gcc builtins for e.g. the round function
> in libm and others.
>
> Therefore this patch adds some glibc variants which are using different
> architecture level sets for s390x.
Do these additional build targets actually result in build breakage?
I'm not sure if anyone does run-time testing on build-many-glibcs.py
output.
I would rather suggest adding an -O3 targets (maybe s390x due to its
inliner differences, and x86-64), where we know we have occasional build
breakage.
Thanks,
Florian
next prev parent reply other threads:[~2020-08-05 15:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 14:45 [PATCH] build-many-glibcs.py: Add some s390x glibc variants Stefan Liebler via Libc-alpha
2020-08-05 15:39 ` Florian Weimer via Libc-alpha [this message]
2020-08-05 17:53 ` Adhemerval Zanella via Libc-alpha
2020-08-06 7:51 ` Stefan Liebler via Libc-alpha
2020-08-06 8:34 ` Florian Weimer via Libc-alpha
2020-08-10 15:34 ` Stefan Liebler via Libc-alpha
2020-08-10 17:23 ` Joseph Myers
2020-08-12 14:22 ` Stefan Liebler via Libc-alpha
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=87bljpumo0.fsf@oldenburg2.str.redhat.com \
--to=libc-alpha@sourceware.org \
--cc=fweimer@redhat.com \
--cc=stli@linux.ibm.com \
/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).