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 middle-end/112087] gimple front end: Simple testcase with array fails to round trip Date: Fri, 27 Oct 2023 12:57:44 +0000 [thread overview] Message-ID: <bug-112087-4-JNuOKxdhwT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112087-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112087 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2023-10-27 Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- "Round-tripping" in the sense of gcc -fdump-tree-X-gimple=- t.c -S | gcc -x c -fgimple - was never the intention. Yes, parsing of CLOBBERs isn't implemented, nor is parsing of "gimple_has_volatile_ops", but since that's redundant info recomputed at update_stmt time we can just scrap it at dump time (but then it's a bit odd to not see it with -gimple ..). It would be nice to have bugreports more specific that "cannot round-trip A or B". Two bugs for this. Parsing of ={v} Parsing of {CLOBBER} (and variants) parsing of ={v} is a bit difficult since it would need to be tentative (there's always a reason why seemingly "easy" things are not yet done). Finding a better syntax for dumping the flags on a stmt might help. Workaround for both: use -fstack-reuse=none
prev parent reply other threads:[~2023-10-27 12:57 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-25 14:08 [Bug middle-end/112087] New: " acoplan at gcc dot gnu.org 2023-10-27 12:57 ` rguenth at gcc dot gnu.org [this message]
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-112087-4-JNuOKxdhwT@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).