public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/113207] [11/12/13/14 Regression] error: type variant has different 'TREE_TYPE' Date: Tue, 02 Jan 2024 20:41:14 +0000 [thread overview] Message-ID: <bug-113207-4-IhO6Rj0nBs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113207-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113207 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[14 Regression] error: type |[11/12/13/14 Regression] |variant has different |error: type variant has |'TREE_TYPE' |different 'TREE_TYPE' Known to fail| |10.0, 9.0 Known to work| |8.1.0 Target Milestone|--- |11.5
next prev parent reply other threads:[~2024-01-02 20:41 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-02 19:40 [Bug lto/113207] New: [14 " doko at gcc dot gnu.org 2024-01-02 19:41 ` [Bug lto/113207] " doko at gcc dot gnu.org 2024-01-02 20:41 ` pinskia at gcc dot gnu.org [this message] 2024-01-02 20:42 ` [Bug c/113207] [11/12/13/14 " pinskia 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-113207-4-IhO6Rj0nBs@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).