public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/109505] (t | 15) & svcntb() causes an OOM/ICE
Date: Mon, 17 Apr 2023 08:07:16 +0000 [thread overview]
Message-ID: <bug-109505-4-7YKBm8E3Rj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109505-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109505
--- Comment #15 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #13)
> (In reply to rsandifo@gcc.gnu.org from comment #12)
> > (In reply to Andrew Pinski from comment #11)
> > > For bit_and/bit_ior, VECTOR_CST (I would assume).
> > Ah, yeah. But then I don't think a top-level POLY_INT_CST_P
> > cuts it. We'd have the same problem with VECTOR_CSTs containing
> > POLY_INT_CSTs.
> Do we really support that?
Sure. At least AIUI, VECTOR_CST can contain whatever constants the
associated scalar supports.
A specific example is:
#include <arm_sve.h>
svint32_t f() { return svdup_s32(svcntw()); }
which gives:
return { POLY_INT_CST [4, 4], ... };
https://godbolt.org/z/T1s3n5Pfx
next prev parent reply other threads:[~2023-04-17 8:07 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 19:21 [Bug c++/109505] New: Compiler loops forever to OOM while compiling evaluate_prg_hwy.cc in Chromium jdapena at igalia dot com
2023-04-13 20:49 ` [Bug c++/109505] " pinskia at gcc dot gnu.org
2023-04-14 8:21 ` jdapena at igalia dot com
2023-04-14 8:23 ` jdapena at igalia dot com
2023-04-14 21:38 ` pinskia at gcc dot gnu.org
2023-04-14 21:53 ` [Bug c++/109505] [12/13 Regression] " pinskia at gcc dot gnu.org
2023-04-14 22:33 ` pinskia at gcc dot gnu.org
2023-04-14 22:40 ` [Bug c++/109505] [12/13 Regression] Compiler loops forever to OOM while compiling evaluate_prg_hwy.cc and SVE pinskia at gcc dot gnu.org
2023-04-14 22:52 ` [Bug middle-end/109505] (t | 15) & svcntb() causes an OOM/ICE pinskia at gcc dot gnu.org
2023-04-16 0:38 ` pinskia at gcc dot gnu.org
2023-04-17 7:03 ` rguenth at gcc dot gnu.org
2023-04-17 7:16 ` rsandifo at gcc dot gnu.org
2023-04-17 7:25 ` pinskia at gcc dot gnu.org
2023-04-17 7:39 ` rsandifo at gcc dot gnu.org
2023-04-17 8:01 ` jakub at gcc dot gnu.org
2023-04-17 8:05 ` rguenther at suse dot de
2023-04-17 8:07 ` rsandifo at gcc dot gnu.org [this message]
2023-05-09 23:47 ` pinskia at gcc dot gnu.org
2023-05-20 7:27 ` sjames at gcc dot gnu.org
2023-05-20 8:15 ` jakub at gcc dot gnu.org
2023-05-21 11:37 ` cvs-commit at gcc dot gnu.org
2023-05-22 13:52 ` cvs-commit at gcc dot gnu.org
2023-05-22 14:09 ` cvs-commit at gcc dot gnu.org
2023-05-22 14:11 ` jakub at gcc dot gnu.org
2023-06-01 8:57 ` herrtimson at yahoo dot de
2023-06-01 10:13 ` jakub at gcc dot gnu.org
2023-06-02 6:56 ` rguenth at gcc dot gnu.org
2023-06-02 7:46 ` cvs-commit at gcc dot gnu.org
2023-06-02 7:46 ` cvs-commit at gcc dot gnu.org
2023-06-02 7:47 ` 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-109505-4-7YKBm8E3Rj@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).