public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "belagod at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/106339] [13 Regression] ICE in exact_div, at poly-int.h:2232 Date: Tue, 06 Sep 2022 08:08:23 +0000 [thread overview] Message-ID: <bug-106339-4-LU5vN912FH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106339-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106339 Tejas Belagod <belagod at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |belagod at gcc dot gnu.org Ever confirmed|0 |1 Last reconfirmed| |2022-09-06 Status|UNCONFIRMED |NEW --- Comment #1 from Tejas Belagod <belagod at gcc dot gnu.org> --- Also breaks my glibc build - ICEs with this test case reduced from glibc/dlfcn/dlinfo.c: /* aarch64-none-linux-gnu-gcc -march=armv8-a+sve -O2 ice.c */ typedef long unsigned int size_t; struct link_map { size_t l_tls_modid; }; # 24 "dlinfo.c" 2 struct dlinfo_args { void *handle; int request; void *arg; }; void dlinfo_doit (void *argsblock) { struct dlinfo_args *const args = argsblock; struct link_map *l = args->handle; *(size_t *) args->arg = 0; *(size_t *) args->arg = l->l_tls_modid; } From my prelimnary investigation, it looks like tree-vect-slp is trying to build the constant vector using duplicate and interleave with 2 V1DI vectors as with the other example posted above. I haven't dug deep enough if V1DI vectors are the right thing to do here.
next prev parent reply other threads:[~2022-09-06 8:08 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-18 8:51 [Bug target/106339] New: " asolokha at gmx dot com 2022-07-18 11:53 ` [Bug target/106339] " rguenth at gcc dot gnu.org 2022-09-06 8:08 ` belagod at gcc dot gnu.org [this message] 2022-10-19 10:42 ` rguenth at gcc dot gnu.org 2022-12-19 23:11 ` pinskia at gcc dot gnu.org 2022-12-21 2:34 ` asolokha at gmx dot com 2022-12-27 12:48 ` marxin 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-106339-4-LU5vN912FH@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: linkBe 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).