From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [PATCH] s390x: Add single instruction math functions
Date: Wed, 14 Jun 2017 19:34:02 -0400 [thread overview]
Message-ID: <20170614233402.GH1627@brightrain.aerifal.cx> (raw)
In-Reply-To: <20170613155513.GB27071@port70.net>
On Tue, Jun 13, 2017 at 05:55:13PM +0200, Szabolcs Nagy wrote:
> > > diff --git a/configure b/configure
> > > index c2db298c..bcaf3a7d 100755
> > > --- a/configure
> > > +++ b/configure
> > > @@ -656,6 +656,12 @@ trycppif __LITTLE_ENDIAN__ "$t" && SUBARCH=${SUBARCH}le
> > > trycppif _SOFT_FLOAT "$t" && fail "$0: error: soft-float not supported on powerpc64"
> > > fi
> > >
> > > +if test "$ARCH" = "s390x" ; then
> > > +echo 'float x; void f(){__asm__("fiebra %0,6,%1,4":"=f"(x):"f"(x));}' > "$tmpc"
> > > +$CC $CFLAGS_C99FSE $CPPFLAGS $CFLAGS -c -o /dev/null "$tmpc" >/dev/null 2>&1 ||
> > > + fail "$0: error: s390x isa level is too low, use at least -march=z196"
> > > +fi
> > > +
> > > if test "$ARCH" = "sh" ; then
> > > tryflag CFLAGS_AUTO -Wa,--isa=any
> > > trycppif __BIG_ENDIAN__ "$t" && SUBARCH=${SUBARCH}eb
> >
> > Why is the x86 configure logic that I used as a template correct?
>
> hm i didnt know about that
> then the patch is probably ok.
The x86 logic is actually implementing policy to the opposite effect,
ignoring the toolchain's default -march and forcing the minimum
baseline isa (i486) unless the user manually puts a specific -march in
CFLAGS. I'm doubtful that it's actually a good idea to be doing that
any more; at least it's inconsistent with how other archs are treated
(using the toolchain's default).
Rich
next prev parent reply other threads:[~2017-06-14 23:34 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 14:51 David Edelsohn
2017-06-10 15:36 ` Szabolcs Nagy
2017-06-10 17:25 ` David Edelsohn
2017-06-10 18:29 ` Szabolcs Nagy
2017-06-10 18:53 ` David Edelsohn
2017-06-10 19:48 ` Rich Felker
2017-06-10 20:22 ` David Edelsohn
2017-06-10 21:28 ` Szabolcs Nagy
2017-06-10 21:44 ` David Edelsohn
2017-06-10 21:48 ` David Edelsohn
2017-06-11 2:20 ` Rich Felker
2017-06-11 10:19 ` Szabolcs Nagy
2017-06-11 15:04 ` Rich Felker
2017-06-11 16:45 ` Szabolcs Nagy
2017-06-11 21:45 ` Rich Felker
2017-06-12 2:46 ` David Edelsohn
2017-06-12 4:36 ` Tuan M. Hoang
2017-06-12 9:03 ` Szabolcs Nagy
2017-06-12 13:28 ` David Edelsohn
2017-06-12 13:54 ` David Edelsohn
2017-06-12 20:28 ` Szabolcs Nagy
2017-06-12 21:02 ` David Edelsohn
2017-06-13 15:55 ` Szabolcs Nagy
2017-06-14 23:34 ` Rich Felker [this message]
2017-06-14 23:40 ` A. Wilcox
2017-06-14 23:44 ` Rich Felker
2017-06-15 12:18 ` David Edelsohn
2017-06-18 17:12 ` David Edelsohn
2017-06-21 0:49 ` Rich Felker
2017-06-21 1:07 ` David Edelsohn
2017-06-21 1:20 ` Rich Felker
2017-06-21 3:34 ` David Edelsohn
2017-06-23 19:31 ` Rich Felker
2017-06-10 21:37 ` Rich Felker
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=20170614233402.GH1627@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.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.
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).