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/23872] .original dump weirdness Date: Wed, 03 Apr 2024 20:50:44 +0000 [thread overview] Message-ID: <bug-23872-4-e26jYU8rha@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-23872-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=23872 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |pinskia at gcc dot gnu.org --- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> --- The <STATEMENT_LIST> issue was fixed with r0-73077-g953ff28998b59b which was included in GCC 4.2.0. The DECL_EXPR issue is still there. Currently the code is: case DECL_EXPR: print_declaration (pp, DECL_EXPR_DECL (node), spc, flags); is_stmt = false; break; I will do a patch to wrap a `DECL_EXPR < ... >` the printing so it becomes obvious what it does.
next parent reply other threads:[~2024-04-03 20:50 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-23872-4@http.gcc.gnu.org/bugzilla/> 2024-04-03 20:50 ` pinskia at gcc dot gnu.org [this message] 2024-04-17 0:18 ` pinskia at gcc dot gnu.org 2024-04-17 1:39 ` [Bug middle-end/23872] " pinskia at gcc dot gnu.org 2024-04-17 1:40 ` pinskia at gcc dot gnu.org 2024-04-17 5:59 ` pinskia at gcc dot gnu.org 2024-05-02 21:40 ` pinskia at gcc dot gnu.org 2024-05-03 22:07 ` cvs-commit at gcc dot gnu.org 2024-05-03 22:13 ` 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-23872-4-e26jYU8rha@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).