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 tree-optimization/113622] [11/12/13/14 Regression] ICE with vectors in named registers
Date: Mon, 29 Jan 2024 09:07:50 +0000 [thread overview]
Message-ID: <bug-113622-4-YAJVCrLZRt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113622-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113622
--- Comment #13 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Xi Ruoyao from comment #12)
> (In reply to Jakub Jelinek from comment #11)
> > I think it is most important we don't ICE and generate correct code. I
> > doubt this is used too much in real-world code, otherwise it would have been
> > reported years ago, so how efficient it will be is less important.
>
> Hmm, but for another test case (LoongArch):
>
> typedef double __attribute__ ((vector_size (32))) vec;
> register vec a asm("f25"), b asm("f26"), c asm("f27");
>
> void
> test (void)
> {
> for (int i = 0; i < 4; i++)
> c[i] = __builtin_isless (a[i], b[i]) ? 0.1 : 0.2;
> }
>
> I'll have to write a loop (because __builtin_isless does not work on
> vectors). Or is there a vector built-in I'm missing?
Why are you doing that?
Normally tests would do
vec
test (vec a, vec b)
{
vec c = {};
for (int i = 0; i < 4; i++)
c[i] = __builtin_isless (a[i], b[i]) ? 0.1 : 0.2;
return c;
}
or something similar.
next prev parent reply other threads:[~2024-01-29 9:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 20:16 [Bug tree-optimization/113622] New: r14-8450 regression: " xry111 at gcc dot gnu.org
2024-01-26 20:23 ` [Bug tree-optimization/113622] " xry111 at gcc dot gnu.org
2024-01-26 20:31 ` [Bug tree-optimization/113622] " pinskia at gcc dot gnu.org
2024-01-26 20:36 ` xry111 at gcc dot gnu.org
2024-01-26 20:39 ` [Bug tree-optimization/113622] [11/12/13/14 Regression] " jakub at gcc dot gnu.org
2024-01-26 20:43 ` pinskia at gcc dot gnu.org
2024-01-26 20:59 ` pinskia at gcc dot gnu.org
2024-01-27 3:49 ` pinskia at gcc dot gnu.org
2024-01-27 12:11 ` jakub at gcc dot gnu.org
2024-01-29 7:56 ` rguenth at gcc dot gnu.org
2024-01-29 8:45 ` rguenth at gcc dot gnu.org
2024-01-29 8:56 ` jakub at gcc dot gnu.org
2024-01-29 8:58 ` xry111 at gcc dot gnu.org
2024-01-29 9:07 ` jakub at gcc dot gnu.org [this message]
2024-01-29 9:09 ` xry111 at gcc dot gnu.org
2024-01-29 9:27 ` rguenth at gcc dot gnu.org
2024-01-29 9:38 ` rguenth at gcc dot gnu.org
2024-01-29 13:31 ` cvs-commit at gcc dot gnu.org
2024-01-29 13:31 ` cvs-commit at gcc dot gnu.org
2024-01-29 13:32 ` [Bug tree-optimization/113622] [11/12/13 " rguenth at gcc dot gnu.org
2024-01-30 8:34 ` cvs-commit at gcc dot gnu.org
2024-01-30 13:22 ` xry111 at gcc dot gnu.org
2024-01-30 13:27 ` xry111 at gcc dot gnu.org
2024-01-30 14:49 ` rguenther at suse dot de
2024-02-25 13:08 ` xry111 at gcc dot gnu.org
2024-03-21 13:54 ` cvs-commit at gcc dot gnu.org
2024-03-21 13:57 ` rguenth at gcc dot gnu.org
2024-05-06 11:49 ` 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-113622-4-YAJVCrLZRt@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).