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 middle-end/23872] .original dump weirdness
Date: Wed, 17 Apr 2024 01:40:11 +0000 [thread overview]
Message-ID: <bug-23872-4-4qcXSiVbdK@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
--- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #7)
> With the example in PR 86698 with the patches I will be posting, gcc now
> does:
> ```
> ;; Function f (null)
> ;; enabled by -tree-original
>
>
> {
> int x = z++ , y;
>
> DECL_EXPR<int x>;
> return x;
> }
>
> ```
>
> I am still deciding if we want to print out the DECL_INIT for the DECL_EXPR
> or not. But this seems like a reasonible output so far.
Oh there is still some confusion around the printing of the DECL_INIT for the
decl. Let me fix that ...
next prev parent reply other threads:[~2024-04-17 1:40 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 ` [Bug c/23872] " pinskia at gcc dot gnu.org
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 [this message]
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-4qcXSiVbdK@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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).