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 middle-end/111683] [11/12/13/14 Regression] Incorrect answer when using SSE2 intrinsics with -O3 since r7-3163-g973625a04b3d9351f2485e37f7d3382af2aed87e
Date: Tue, 12 Mar 2024 02:44:38 +0000	[thread overview]
Message-ID: <bug-111683-4-gqzjWWdSR8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111683-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Created attachment 57678
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57678&action=edit
testcase that fails all the way back to GCC 4.8.x

This one fails until GCC 4.8.1, works in GCC 4.7.4 but that is because the
outer loop is unrolled in GCC 4.7.4.

  parent reply	other threads:[~2024-03-12  2:44 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-03 18:27 [Bug c++/111683] New: Incorrect answer when using SSE2 intrinsics with -O3 deodharvinit99 at gmail dot com
2023-10-03 22:18 ` [Bug middle-end/111683] [11/12/13/14 Regression] " pinskia at gcc dot gnu.org
2023-10-04  9:55 ` rguenth at gcc dot gnu.org
2023-10-04 16:56 ` amonakov at gcc dot gnu.org
2023-12-12 10:27 ` jakub at gcc dot gnu.org
2024-03-07 21:06 ` law at gcc dot gnu.org
2024-03-10  5:55 ` [Bug middle-end/111683] [11/12/13/14 Regression] Incorrect answer when using SSE2 intrinsics with -O3 since r7-3163-g973625a04b3d9351f2485e37f7d3382af2aed87e kugan at gcc dot gnu.org
2024-03-10 11:15 ` sjames at gcc dot gnu.org
2024-03-12  1:58 ` pinskia at gcc dot gnu.org
2024-03-12  2:24 ` pinskia at gcc dot gnu.org
2024-03-12  2:31 ` pinskia at gcc dot gnu.org
2024-03-12  2:44 ` pinskia at gcc dot gnu.org [this message]
2024-03-12 13:23 ` jakub at gcc dot gnu.org
2024-03-19 17:28 ` jakub at gcc dot gnu.org
2024-03-19 18:17 ` pinskia at gcc dot gnu.org
2024-03-21 16:47 ` jakub at gcc dot gnu.org
2024-03-22  7:33 ` rguenth at gcc dot gnu.org
2024-03-22  7:38 ` rguenth at gcc dot gnu.org
2024-03-22  7:47 ` jakub at gcc dot gnu.org
2024-03-22  7:50 ` jakub at gcc dot gnu.org
2024-03-22  8:06 ` rguenth at gcc dot gnu.org
2024-03-22  8:18 ` jakub at gcc dot gnu.org
2024-03-22 10:37 ` jakub at gcc dot gnu.org
2024-03-22 10:46 ` jakub at gcc dot gnu.org
2024-03-22 11:35 ` rguenth at gcc dot gnu.org
2024-03-22 11:43 ` jakub at gcc dot gnu.org
2024-03-22 12:42 ` rguenther at suse dot de
2024-03-23 10:18 ` cvs-commit at gcc dot gnu.org
2024-03-23 10:21 ` [Bug middle-end/111683] [11/12/13 " jakub at gcc dot gnu.org
2024-03-30  3:55 ` cvs-commit 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-111683-4-gqzjWWdSR8@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).