From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gcc-patches:master commit in: 10.2.0/gentoo/
Date: Mon, 27 Jul 2020 06:50:36 +0000 (UTC) [thread overview]
Message-ID: <1595832534.fafbb4148cb5c2cf7e1ae02679240cba43e95992.slyfox@gentoo> (raw)
commit: fafbb4148cb5c2cf7e1ae02679240cba43e95992
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Mon Jul 27 06:48:54 2020 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Mon Jul 27 06:48:54 2020 +0000
URL: https://gitweb.gentoo.org/proj/gcc-patches.git/commit/?id=fafbb414
10.2.0: backport ICE on invalid function declarations
Reported-by: Jack Ostroff
Bug: https://bugs.gentoo.org/730406
Bug: https://gcc.gnu.org/PR95820
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
10.2.0/gentoo/34_all_fundecl-ICE-PR95820.patch | 25 +++++++++++++++++++++++++
10.2.0/gentoo/README.history | 1 +
2 files changed, 26 insertions(+)
diff --git a/10.2.0/gentoo/34_all_fundecl-ICE-PR95820.patch b/10.2.0/gentoo/34_all_fundecl-ICE-PR95820.patch
new file mode 100644
index 0000000..e365420
--- /dev/null
+++ b/10.2.0/gentoo/34_all_fundecl-ICE-PR95820.patch
@@ -0,0 +1,25 @@
+It's an unofficial backport of PR95820 where gcc ICEs on
+invalid syntax. As creduce frequently end up in these ICEs
+as in #730406 let's backport it to gcc-10.
+
+https://gcc.gnu.org/PR95820
+https://bugs.gentoo.org/730406
+--- a/gcc/cp/decl.c
++++ b/gcc/cp/decl.c
+@@ -12029,14 +12029,11 @@ grokdeclarator (const cp_declarator *declarator,
+
+ /* Handle a late-specified return type. */
+ tree late_return_type = declarator->u.function.late_return_type;
+- if (funcdecl_p
+- /* This is the case e.g. for
+- using T = auto () -> int. */
+- || inner_declarator == NULL)
++ if (true)
+ {
+ if (tree auto_node = type_uses_auto (type))
+ {
+- if (!late_return_type)
++ if (!late_return_type && funcdecl_p)
+ {
+ if (current_class_type
+ && LAMBDA_TYPE_P (current_class_type))
diff --git a/10.2.0/gentoo/README.history b/10.2.0/gentoo/README.history
index 1c0fff9..7cde6a3 100644
--- a/10.2.0/gentoo/README.history
+++ b/10.2.0/gentoo/README.history
@@ -1,5 +1,6 @@
2 TODO
+ 33_all_lto-O0-mix-ICE-ipa-PR96291.patch
+ + 34_all_fundecl-ICE-PR95820.patch
1 23 July 2020
+ 01_all_default-fortify-source.patch
next reply other threads:[~2020-07-27 6:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 6:50 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-08 19:36 [gentoo-commits] proj/gcc-patches:master commit in: 10.2.0/gentoo/ Sergei Trofimovich
2021-03-19 8:02 Sergei Trofimovich
2021-03-15 22:57 Sergei Trofimovich
2021-03-04 11:02 Sergei Trofimovich
2020-12-29 10:07 Sergei Trofimovich
2020-12-29 9:55 Sergei Trofimovich
2020-12-29 9:55 Sergei Trofimovich
2020-12-01 19:18 Sergei Trofimovich
2020-11-04 7:47 Sergei Trofimovich
2020-10-15 17:32 Sergei Trofimovich
2020-10-02 9:33 Sergei Trofimovich
2020-10-02 9:13 Sergei Trofimovich
2020-09-10 21:38 Sergei Trofimovich
2020-09-03 17:12 Sergei Trofimovich
2020-08-23 9:14 Sergei Trofimovich
2020-08-17 21:26 Sergei Trofimovich
2020-08-13 9:04 Sergei Trofimovich
2020-07-26 10:35 Sergei Trofimovich
2020-07-23 8:42 Sergei Trofimovich
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=1595832534.fafbb4148cb5c2cf7e1ae02679240cba43e95992.slyfox@gentoo \
--to=slyfox@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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