public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/103688] New: [11 regression] build error after r11-9380
Date: Mon, 13 Dec 2021 17:41:06 +0000 [thread overview]
Message-ID: <bug-103688-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103688
Bug ID: 103688
Summary: [11 regression] build error after r11-9380
Product: gcc
Version: 11.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
g:f2cc8d059df8aea1b811a4a68512d137f4e83bd5, r11-9380
commit f2cc8d059df8aea1b811a4a68512d137f4e83bd5 (HEAD, origin/releases/gcc-11)
Author: Joel Hutton <joel.hutton@arm.com>
Date: Fri Dec 10 10:26:42 2021 +0000
pr103523: Check for PLUS/MINUS support
. . .
gcc/ChangeLog:
* tree-vect-loop.c (vectorizable_induction): Check for
This breaks the build of gcc 11:
g++ -fno-PIE -c -g -O2 -DIN_GCC -fno-exceptions -fno-rtti
-fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings
-Wcast-qual -Wmissing-format-attribute -Woverloaded-virtual -pedantic
-Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H
-I. -I. -I/home/seurer/gcc/git/gcc-11/gcc -I/home/seurer/gcc/git/gcc-11/gcc/.
-I/home/seurer/gcc/git/gcc-11/gcc/../include
-I/home/seurer/gcc/git/gcc-11/gcc/../libcpp/include
-I/home/seurer/gcc/git/gcc-11/gcc/../libcody
-I/home/seurer/gcc/git/build/gcc-11/./gmp -I/home/seurer/gcc/git/gcc-11/gmp
-I/home/seurer/gcc/git/build/gcc-11/./mpfr/src
-I/home/seurer/gcc/git/gcc-11/mpfr/src -I/home/seurer/gcc/git/gcc-11/mpc/src
-I/home/seurer/gcc/git/gcc-11/gcc/../libdecnumber
-I/home/seurer/gcc/git/gcc-11/gcc/../libdecnumber/dpd -I../libdecnumber
-I/home/seurer/gcc/git/gcc-11/gcc/../libbacktrace
-I/home/seurer/gcc/git/build/gcc-11/./isl/include
-I/home/seurer/gcc/git/gcc-11/isl/include -o tree-vect-loop.o -MT
tree-vect-loop.o -MMD -MP -MF ./.deps/tree-vect-loop.TPo
/home/seurer/gcc/git/gcc-11/gcc/tree-vect-loop.c
/home/seurer/gcc/git/gcc-11/gcc/tree-vect-loop.c: In function 'bool
vectorizable_induction(loop_vec_info, stmt_vec_info, gimple**, slp_tree,
stmt_vector_for_cost*)':
/home/seurer/gcc/git/gcc-11/gcc/tree-vect-loop.c:8000:8: error:
'directly_supported_p' was not declared in this scope
8000 | if (!directly_supported_p (PLUS_EXPR, step_vectype)
| ^~~~~~~~~~~~~~~~~~~~
make[2]: *** [Makefile:1142: tree-vect-loop.o] Error 1
next reply other threads:[~2021-12-13 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 17:41 seurer at gcc dot gnu.org [this message]
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
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@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).