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 19:35:42 +0000 [thread overview] Message-ID: <bug-94587-4-xyt0d91hmV@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 #5 from Patrick J. LoPresti <lopresti at gmail dot com> --- (In reply to Andrew Pinski from comment #4) > > Note this is true even without using intrinsics really. You can get the > same behavior you are seeing with using standard C code. Yes, which is one reason I am using intrinsics: They provide deterministic behavior on literally every compiler at every optimization level by default. Except GCC when AVX512 is enabled, that is. > > > > Wouldn't fp-contract be more appropriate as part of "-ffast-math"? > > No. This has been discussed many times and decided no. A ridiculous but not surprising decision. > https://gcc.gnu.org/onlinedocs/gcc-9.3.0/gcc/Floating-point-implementation. > html#Floating-point-implementation Well, that page is wrong. "Expressions are currently only contracted if -ffp-contract=fast, -funsafe-math-optimizations or -ffast-math are used." 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. More to the point, it does not answer the question I asked, which is what options are required to get deterministic behavior from intrinsics. So I suppose I have to re-read that chapter on every release, then search the rest of the documentation to learn what the defaults are, to figure out whether and how you broke something further? OK thanks
next prev parent reply other threads:[~2020-04-14 19:35 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 [this message] 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
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-xyt0d91hmV@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: linkBe 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).