public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99459] New: [11 Regression] Many coroutines regressions on armv7hl-linux-gnueabi
Date: Mon, 08 Mar 2021 09:26:34 +0000 [thread overview]
Message-ID: <bug-99459-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99459
Bug ID: 99459
Summary: [11 Regression] Many coroutines regressions on
armv7hl-linux-gnueabi
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: jakub at gcc dot gnu.org
Target Milestone: ---
Seems likely one of the last weeks coroutines change broke a lot of coroutine
tests on 32-bit arm:
FAIL: g++.dg/coroutines/coro-missing-initial-suspend.C (test for excess errors)
FAIL: g++.dg/coroutines/pr94886-folly-3.C (internal compiler error)
FAIL: g++.dg/coroutines/pr94886-folly-3.C (test for excess errors)
FAIL: g++.dg/coroutines/pr95599.C (internal compiler error)
FAIL: g++.dg/coroutines/pr95599.C (test for excess errors)
FAIL: g++.dg/coroutines/pr95616-2.C (internal compiler error)
FAIL: g++.dg/coroutines/pr95616-2.C (test for errors, line 28)
FAIL: g++.dg/coroutines/pr95616-2.C (test for excess errors)
FAIL: g++.dg/coroutines/pr95616-3.C (internal compiler error)
FAIL: g++.dg/coroutines/pr95616-3.C (test for errors, line 19)
FAIL: g++.dg/coroutines/pr95616-3.C (test for excess errors)
FAIL: g++.dg/coroutines/pr95616-4.C (internal compiler error)
FAIL: g++.dg/coroutines/pr95616-4.C (test for errors, line 20)
FAIL: g++.dg/coroutines/pr95616-4.C (test for excess errors)
...
FAIL: g++.dg/coroutines/torture/pr95003.C -O1 (internal compiler error)
FAIL: g++.dg/coroutines/torture/pr95003.C -O1 (test for excess errors)
FAIL: g++.dg/coroutines/torture/pr95003.C -O2 (internal compiler error)
FAIL: g++.dg/coroutines/torture/pr95003.C -O2 (test for excess errors)
FAIL: g++.dg/coroutines/torture/pr95003.C -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions (internal compiler
error)
FAIL: g++.dg/coroutines/torture/pr95003.C -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess
errors)
FAIL: g++.dg/coroutines/torture/pr95003.C -O3 -g (internal compiler error)
FAIL: g++.dg/coroutines/torture/pr95003.C -O3 -g (test for excess errors)
FAIL: g++.dg/coroutines/torture/pr95003.C -Os (internal compiler error)
FAIL: g++.dg/coroutines/torture/pr95003.C -Os (test for excess errors)
FAIL: g++.dg/coroutines/torture/pr95003.C -O2 -flto -fno-use-linker-plugin
-flto-partition=none (internal compiler error)
FAIL: g++.dg/coroutines/torture/pr95003.C -O2 -flto -fno-use-linker-plugin
-flto-partition=none (test for excess errors)
FAIL: g++.dg/coroutines/torture/pr95003.C -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects (internal compiler error)
FAIL: g++.dg/coroutines/torture/pr95003.C -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects (test for excess errors)
Typical ICEs are like:
0x3c7de7 crash_signal
../../gcc/toplev.c:328
0x1e301b build_co_await
../../gcc/cp/coroutines.cc:871
0x1e52ab build_init_or_final_await
../../gcc/cp/coroutines.cc:2628
0x1e52ab coro_rewrite_function_body
../../gcc/cp/coroutines.cc:4023
0x1e52ab morph_fn_to_coro(tree_node*, tree_node**, tree_node**)
../../gcc/cp/coroutines.cc:4166
0x7b045f finish_function(bool)
../../gcc/cp/decl.c:17207
or
0x3c7de7 crash_signal
../../gcc/toplev.c:328
0x1e34af build_co_await
../../gcc/cp/coroutines.cc:1034
0x1e52ab build_init_or_final_await
../../gcc/cp/coroutines.cc:2628
0x1e52ab coro_rewrite_function_body
../../gcc/cp/coroutines.cc:4023
0x1e52ab morph_fn_to_coro(tree_node*, tree_node**, tree_node**)
../../gcc/cp/coroutines.cc:4166
0x7b045f finish_function(bool)
../../gcc/cp/decl.c:17207
next reply other threads:[~2021-03-08 9:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 9:26 jakub at gcc dot gnu.org [this message]
2021-03-08 9:30 ` [Bug c++/99459] " clyon at gcc dot gnu.org
2021-03-08 9:35 ` jakub at gcc dot gnu.org
2021-03-08 9:54 ` jakub at gcc dot gnu.org
2021-03-08 9:54 ` jakub at gcc dot gnu.org
2021-03-08 9:55 ` jakub at gcc dot gnu.org
2021-03-08 9:56 ` iains at gcc dot gnu.org
2021-03-08 9:59 ` iains at gcc dot gnu.org
2021-03-08 10:01 ` rguenth at gcc dot gnu.org
2021-03-08 10:03 ` iains at gcc dot gnu.org
2021-03-08 10:08 ` jakub at gcc dot gnu.org
2021-03-08 14:27 ` iains at gcc dot gnu.org
2021-03-08 14:38 ` jakub at gcc dot gnu.org
2021-03-09 11:55 ` jakub at gcc dot gnu.org
2021-03-09 15:46 ` cvs-commit at gcc dot gnu.org
2021-03-09 15:48 ` jakub 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-99459-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).