public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/115115] [12/13/14/15 Regression] highway-1.0.7 wrong _mm_cvttps_epi32() constant fold
Date: Thu, 16 May 2024 09:14:38 +0000	[thread overview]
Message-ID: <bug-115115-4-lhkbJcLLW3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115115-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
It depends on if you consider a float to int conversion or not. For (long
long)float . The value if the float was out of range is unspecified so
returning one value or another is both valid.
So the question is it corresponding to float to integer conversion in c or
exactly what the instruction does. The later has implications across the board.

  parent reply	other threads:[~2024-05-16  9:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-15 21:38 [Bug target/115115] New: " slyfox at gcc dot gnu.org
2024-05-15 21:45 ` [Bug target/115115] " slyfox at gcc dot gnu.org
2024-05-15 21:49 ` pinskia at gcc dot gnu.org
2024-05-15 22:00 ` slyfox at gcc dot gnu.org
2024-05-16  0:36 ` liuhongt at gcc dot gnu.org
2024-05-16  7:12 ` rguenth at gcc dot gnu.org
2024-05-16  9:08 ` slyfox at gcc dot gnu.org
2024-05-16  9:14 ` pinskia at gcc dot gnu.org [this message]
2024-05-16 21:57 ` slyfox at gcc dot gnu.org
2024-05-17  8:27 ` jan.wassenberg at gmail dot com
2024-05-17  9:22 ` jan.wassenberg at gmail dot com
2024-05-17 18:10 ` jan.wassenberg at gmail dot com
2024-05-20 13:56 ` slyfox at gcc dot gnu.org
2024-05-20 15:48 ` jan.wassenberg at gmail dot com
2024-06-05  4:09 ` cvs-commit at gcc dot gnu.org
2024-06-05  9:12 ` slyfox at gcc dot gnu.org
2024-06-20  9:15 ` rguenth 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-115115-4-lhkbJcLLW3@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).