public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vincent-gcc at vinc17 dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/323] optimized code gives strange floating point results
Date: Wed, 05 Jul 2023 20:15:18 +0000 [thread overview]
Message-ID: <bug-323-4-NY0k6bNffH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-323-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=323
--- Comment #227 from Vincent Lefèvre <vincent-gcc at vinc17 dot net> ---
In "See Also", there are several bugs that are related only to vectorization
optimizations. What is the relation with this bug?
For instance, PR89653 is "GCC (trunk and all earlier versions) fails to
vectorize (SSE/AVX2/AVX-512) the following loop [...]". If this is
SSE/AVX2/AVX-512, where does x86 extended precision occur?
next prev parent reply other threads:[~2023-07-05 20:15 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-323-4@http.gcc.gnu.org/bugzilla/>
2010-10-05 19:00 ` pinskia at gcc dot gnu.org
2011-01-13 22:10 ` pinskia at gcc dot gnu.org
2011-02-21 12:47 ` rguenth at gcc dot gnu.org
2011-03-08 19:11 ` acfbuerger at googlemail dot com
2011-03-22 16:14 ` rguenth at gcc dot gnu.org
2012-01-13 6:33 ` pinskia at gcc dot gnu.org
2012-04-24 8:23 ` rguenth at gcc dot gnu.org
2012-11-12 14:54 ` paolo.carlini at oracle dot com
2012-11-30 18:08 ` pinskia at gcc dot gnu.org
2012-12-15 2:10 ` soren.sandmann at gmail dot com
2012-12-31 16:13 ` rguenth at gcc dot gnu.org
2013-01-30 8:58 ` jakub at gcc dot gnu.org
2013-04-26 16:07 ` ondrej at sury dot org
2013-06-24 10:53 ` rguenth at gcc dot gnu.org
2013-11-18 18:47 ` dominiq at lps dot ens.fr
2014-01-02 8:35 ` Martin.vGagern at gmx dot net
2014-06-27 0:07 ` pinskia at gcc dot gnu.org
2014-12-30 18:45 ` manu at gcc dot gnu.org
2014-12-30 19:16 ` manu at gcc dot gnu.org
2014-12-31 0:00 ` vincent-gcc at vinc17 dot net
2014-12-31 0:45 ` manu at gcc dot gnu.org
2015-01-26 19:05 ` schwab@linux-m68k.org
2015-05-29 16:50 ` jsm28 at gcc dot gnu.org
2020-04-29 18:01 ` pinskia at gcc dot gnu.org
2021-05-31 3:46 ` pinskia at gcc dot gnu.org
2021-09-02 7:41 ` pinskia at gcc dot gnu.org
2021-10-27 7:55 ` jessicaking07 at protonmail dot com
2021-11-02 7:17 ` pinskia at gcc dot gnu.org
2021-11-05 23:18 ` timturnerc at yahoo dot com
2022-07-02 2:09 ` pinskia at gcc dot gnu.org
2022-10-14 7:32 ` cvs-commit at gcc dot gnu.org
2023-07-05 19:22 ` pinskia at gcc dot gnu.org
2023-07-05 20:15 ` vincent-gcc at vinc17 dot net [this message]
2023-07-05 21:00 ` vincent-gcc at vinc17 dot net
2023-07-11 8:25 ` malat at debian dot org
2023-09-21 13:34 ` pinskia at gcc dot gnu.org
2024-01-31 8:52 ` pinskia 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-323-4-NY0k6bNffH@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).