public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/96591] [8/9/10/11 Regression] ICE with -flto=auto and -O1: tree code ‘typename_type’ is not supported in LTO streams Date: Tue, 25 Aug 2020 09:27:44 +0000 [thread overview] Message-ID: <bug-96591-4-eumjLaLmBo@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 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|lto |c++ Target Milestone|--- |8.5 Keywords| |lto --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- FE trees should not leak into the middle-end so it looks more like a FE issue to me. We're chasing TYPE_FIELDS of the context of the scalar_type name and visiting a TEMPLATE_DECL for 'rebind' in simd_traits. In the end this might mean free-lang-data doesn't visit DECL_CONTEXT of the INTEGER_TYPEs TYPE_NAME? At least I do not see it walking simd_traits. It might also be that some intermediate optimization somehow introduces a reference to this type from nowhere (huh).
next prev parent reply other threads:[~2020-08-25 9:27 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 ` rguenth at gcc dot gnu.org [this message] 2020-08-25 12:12 ` [Bug c++/96591] [8/9/10/11 Regression] " 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 ` [Bug lto/96591] [8/9 " cvs-commit at gcc dot gnu.org 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-eumjLaLmBo@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).