public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/103688] [11 regression] build error after r11-9380 Date: Tue, 14 Dec 2021 12:49:58 +0000 [thread overview] Message-ID: <bug-103688-4-BmeRALzuxT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103688-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103688 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Joel Hutton <joelh@gcc.gnu.org>: https://gcc.gnu.org/g:9a5b3c50e26c24814ede693600fb24e4c7b6c60c commit r11-9382-g9a5b3c50e26c24814ede693600fb24e4c7b6c60c Author: Joel Hutton <joel.hutton@arm.com> Date: Tue Dec 14 12:01:09 2021 +0000 vect-loop: fix build Previous commit broke build as it relied on directly_supported_p which is not in 11. This reworks to avoid using directly_supported_p. gcc/ChangeLog: PR bootstrap/103688 * tree-vect-loop.c (vectorizable_induction): Rework to avoid directly_supported_p.
next prev parent reply other threads:[~2021-12-14 12:49 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-13 17:41 [Bug bootstrap/103688] New: " seurer at gcc dot gnu.org 2021-12-14 6:29 ` [Bug bootstrap/103688] " marxin at gcc dot gnu.org 2021-12-14 12:49 ` cvs-commit at gcc dot gnu.org [this message] 2021-12-15 9:27 ` joelh 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-103688-4-BmeRALzuxT@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).