public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/99497] _mm_min_ss/_mm_max_ss incorrect results when values known at compile time
Date: Tue, 09 Mar 2021 23:14:09 +0000	[thread overview]
Message-ID: <bug-99497-4-YtORJNXcwj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99497-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
And another question is if we without -ffast-math ever create MIN_EXPR/MAX_EXPR
and what exactly are the rules for those, if it is safe to expand those into
SMAX etc., or if those need to use UNSPECs too.

  parent reply	other threads:[~2021-03-09 23:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-09 22:43 [Bug c++/99497] New: " scott_sas_smith at hotmail dot com
2021-03-09 23:12 ` [Bug target/99497] " jakub at gcc dot gnu.org
2021-03-09 23:14 ` jakub at gcc dot gnu.org [this message]
2021-03-10  8:15 ` rguenth at gcc dot gnu.org
2021-03-10  8:35 ` jakub at gcc dot gnu.org

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-99497-4-YtORJNXcwj@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).