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 lto/96591] [8/9 Regression] ICE with -flto=auto and -O1: tree code ‘typename_type’ is not supported in LTO streams Date: Mon, 12 Apr 2021 11:23:39 +0000 [thread overview] Message-ID: <bug-96591-4-00glwxxUuS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96591-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96591 --- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-9 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:c0ae84d67a61512ec36d5c82ae52090c4b6440d1 commit r9-9341-gc0ae84d67a61512ec36d5c82ae52090c4b6440d1 Author: Richard Biener <rguenther@suse.de> Date: Mon Feb 8 09:52:56 2021 +0100 lto/96591 - walk VECTOR_CST elements in walk_tree This implements walking of VECTOR_CST elements in walk_tree, mimicing the walk of COMPLEX_CST elements. Without this free-lang-data fails to see some types in case they are only refered to via tree constants used only as VECTOR_CST elements. 2021-02-08 Richard Biener <rguenther@suse.de> PR lto/96591 * tree.c (walk_tree_1): Walk VECTOR_CST elements. * g++.dg/lto/pr96591_0.C: New testcase. (cherry picked from commit d4536e431316b4568e236afd7a6017e5efd1b0a1)
next prev parent reply other threads:[~2021-04-12 11:23 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-12 15:58 [Bug lto/96591] New: " gcc-bugs at marehr dot dialup.fu-berlin.de 2020-08-12 17:05 ` [Bug lto/96591] " marxin at gcc dot gnu.org 2020-08-25 9:27 ` [Bug c++/96591] [8/9/10/11 Regression] " rguenth at gcc dot gnu.org 2020-08-25 12:12 ` jakub at gcc dot gnu.org 2020-08-26 5:20 ` asolokha at gmx dot com 2020-10-12 12:34 ` rguenth at gcc dot gnu.org 2021-02-04 21:03 ` jason at gcc dot gnu.org 2021-02-06 6:20 ` [Bug lto/96591] " jason at gcc dot gnu.org 2021-02-08 7:47 ` rguenth at gcc dot gnu.org 2021-02-08 8:45 ` rguenth at gcc dot gnu.org 2021-02-08 12:05 ` cvs-commit at gcc dot gnu.org 2021-02-08 12:06 ` [Bug lto/96591] [8/9/10 " rguenth at gcc dot gnu.org 2021-03-24 14:26 ` cvs-commit at gcc dot gnu.org 2021-04-12 11:23 ` cvs-commit at gcc dot gnu.org [this message] 2021-04-26 10:46 ` [Bug lto/96591] [8 " cvs-commit at gcc dot gnu.org 2021-04-26 10:48 ` rguenth 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-96591-4-00glwxxUuS@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).