public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Tulio Magno Quites Machado Filho <tuliom@ascii.art.br>
To: Paul Zimmermann <Paul.Zimmermann@inria.fr>
Cc: fweimer@redhat.com, libc-alpha@sourceware.org
Subject: Re: use of fma
Date: Wed, 28 Apr 2021 12:45:24 -0300	[thread overview]
Message-ID: <87fszaza3v.fsf@linux.ibm.com> (raw)
In-Reply-To: <mwim46o2ta.fsf@tomate.loria.fr>

Paul Zimmermann <Paul.Zimmermann@inria.fr> writes:

>> Side note: single and double-precision multiply-add have been available since
>> the PPC ISA and POWER1 ISA respectively.
>> So, they're also available by default on powerpc64 and powerpc builds
>> supporting hw fpu.
>
> thank you Tulio Magno. By the way, does anyone know of any hardware with
> extended double and/or quadruple precision multiply-add?

That's a good example of FMA that is not available by default on any of the
ABIs because it has been added to the POWER ISA 3.0 (e.g. POWER9).  :-D

You need a new enough compiler (GCC >= 7.4), but you can use gcc135 (POWER9)
from the GCC Compile Farm project:

[tuliom@gcc135 ~]$ /opt/at12.0/bin/gcc -O2 -mcpu=power9 -g -dM -E -xc /dev/null | grep __FP_FAST_FMA
#define __FP_FAST_FMAF128 1
#define __FP_FAST_FMAF 1
#define __FP_FAST_FMAF64x 1
#define __FP_FAST_FMAF32 1
#define __FP_FAST_FMAF64 1
#define __FP_FAST_FMAF32x 1
#define __FP_FAST_FMA 1

Notice I used -mcpu instead of -march.

-- 
Tulio Magno

  reply	other threads:[~2021-04-28 15:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28  7:23 Paul Zimmermann
2021-04-28  8:25 ` Florian Weimer
2021-04-28  8:42   ` Paul Zimmermann
2021-04-28  9:06     ` Florian Weimer
2021-04-28 17:29     ` Joseph Myers
2021-04-28 15:00   ` Tulio Magno Quites Machado Filho
2021-04-28 15:18     ` Paul Zimmermann
2021-04-28 15:45       ` Tulio Magno Quites Machado Filho [this message]
2021-04-28 17:46         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fszaza3v.fsf@linux.ibm.com \
    --to=tuliom@ascii.art.br \
    --cc=Paul.Zimmermann@inria.fr \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@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).