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/109505] (t | 15) & svcntb() causes an OOM/ICE
Date: Fri, 14 Apr 2023 22:52:25 +0000 [thread overview]
Message-ID: <bug-109505-4-l7gAdJggAc@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
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Target Milestone|12.3 |---
Component|c++ |middle-end
Ever confirmed|0 |1
Last reconfirmed|2023-04-13 00:00:00 |2023-04-14
Summary|[12/13 Regression] Compiler |(t | 15) & svcntb() causes
|loops forever to OOM while |an OOM/ICE
|compiling |
|evaluate_prg_hwy.cc and SVE |
Known to fail| |11.1.0, 13.0
--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Simple reduced testcase:
```
#include <arm_sve.h>
unsigned long f(unsigned long tt)
{
unsigned long t= svcntb();
return (tt | 15) & t;
}
```
Confirmed.
Fails even in GCC 11.1.0.
It is due to match.pd's
/* (x | CST1) & CST2 -> (x & CST2) | (CST1 & CST2) */
(simplify
(bit_and (bit_ior @0 CONSTANT_CLASS_P@1) CONSTANT_CLASS_P@2)
(bit_ior (bit_and @0 @2) (bit_and @1 @2)))
POLY_INT_CST is a CONSTANT_CLASS but does not simplify on the bit_and.
So maybe it should include a ! on the (bit_and @1 @2) .
next prev parent reply other threads:[~2023-04-14 22:52 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 ` pinskia at gcc dot gnu.org [this message]
2023-04-16 0:38 ` [Bug middle-end/109505] (t | 15) & svcntb() causes an OOM/ICE 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
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-l7gAdJggAc@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).