public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/96037] [11 regression] ICE at tree-ssa-loop.c:414 after r11-1782 Date: Fri, 03 Jul 2020 07:22:43 +0000 [thread overview] Message-ID: <bug-96037-4-jqB2cnCcOb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96037-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96037 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |WAITING --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- So I'm guessing this is powerpc64be from your command line but with a cc1 cross configured as ./configure --target=powerpc64-suse-linux I cannot reproduce this: gcc> ./cc1 -quiet simd-15.c -I include -O2 -fopenmp adding various -mcpu or -mvsx / -maltivec doesn't help either but any of -mvsx or -maltivec are required to have the vectorizer run at all. So ...?
next prev parent reply other threads:[~2020-07-03 7:22 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-02 19:34 [Bug tree-optimization/96037] New: " seurer at linux dot vnet.ibm.com 2020-07-03 6:48 ` [Bug tree-optimization/96037] " rguenth at gcc dot gnu.org 2020-07-03 7:22 ` rguenth at gcc dot gnu.org [this message] 2020-07-03 7:30 ` marxin at gcc dot gnu.org 2020-07-03 8:24 ` rguenth at gcc dot gnu.org 2020-07-03 8:31 ` marxin at gcc dot gnu.org 2020-07-03 9:33 ` rguenth at gcc dot gnu.org 2020-07-03 10:52 ` cvs-commit at gcc dot gnu.org 2020-07-03 10:53 ` 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-96037-4-jqB2cnCcOb@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).