public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lopresti at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/94587] Intrinsics optimization bug with -O2 -march=skylake-avx512
Date: Tue, 14 Apr 2020 21:33:45 +0000	[thread overview]
Message-ID: <bug-94587-4-irPS2ThrUB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94587-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94587

--- Comment #8 from Patrick J. LoPresti <lopresti at gmail dot com> ---
(In reply to Andrew Pinski from comment #6)
> (In reply to Patrick J. LoPresti from comment #5)
> > I did not use -ffp-contract=fast nor -funsafe-math-optimizations nor
> > -ffast-math. Yet the statements were contracted. So the documentation has a
> > bug.
> 
> Not exactly because the defualt for -std=c11 is different from -std=gnu11
> (which is the default, or is the default -std=gnu17 well it depends on the
> compiler version).

Yes, I know. So the floating-point implementation chapter can only be
understood if you also search the rest of the 1000-page documentation to learn
what the defaults are. And then repeat for every release because "This is
subject to change."

(In reply to Jakub Jelinek from comment #7)
> Note, clang defaults to -ffp-contract=on which is like =fast (except when
> you use FP_CONTRACT pragma).

No, it is not like "fast". At least, not according to my experience and this
StackOverflow answer:

https://stackoverflow.com/a/43357638

Note the link to the live example on gcc.godbolt.org.

      parent reply	other threads:[~2020-04-14 21:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-13 21:28 [Bug rtl-optimization/94587] New: " lopresti at gmail dot com
2020-04-14  6:47 ` [Bug target/94587] " marxin at gcc dot gnu.org
2020-04-14  9:27 ` jakub at gcc dot gnu.org
2020-04-14 15:25 ` lopresti at gmail dot com
2020-04-14 18:51 ` pinskia at gcc dot gnu.org
2020-04-14 19:35 ` lopresti at gmail dot com
2020-04-14 20:44 ` pinskia at gcc dot gnu.org
2020-04-14 20:47 ` jakub at gcc dot gnu.org
2020-04-14 21:33 ` lopresti at gmail dot com [this message]

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=bug-94587-4-irPS2ThrUB@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).