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/97666] [11 Regression] bootstrap fail for powerpc-darwin while building libgfortran after r11-4485 Date: Mon, 02 Nov 2020 07:50:52 +0000 [thread overview] Message-ID: <bug-97666-4-tNKRCb3wyc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97666-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97666 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |11.0 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Hmm, in vectorizable_operation () can you try (gdb) p debug (slp_node) ? If r11-4485 is the correct bisect point -fdump-tree-slp-details before/after this rev might also provide a clue ...
next prev parent reply other threads:[~2020-11-02 7:50 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-01 19:48 [Bug tree-optimization/97666] New: " iains at gcc dot gnu.org 2020-11-01 19:50 ` [Bug tree-optimization/97666] " iains at gcc dot gnu.org 2020-11-02 7:50 ` rguenth at gcc dot gnu.org [this message] 2020-11-03 12:33 ` cvs-commit at gcc dot gnu.org 2020-11-03 12:41 ` rguenth at gcc dot gnu.org 2020-11-04 8:37 ` cvs-commit 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-97666-4-tNKRCb3wyc@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).