public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/102605] address instruction from -fdump-tree-*-gimple doesn't work with -fgimple Date: Wed, 06 Oct 2021 06:11:15 +0000 [thread overview] Message-ID: <bug-102605-4-fj08cBESI1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102605-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102605 --- Comment #4 from rguenther at suse dot de <rguenther at suse dot de> --- On Tue, 5 Oct 2021, aldyh at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102605 > > --- Comment #2 from Aldy Hernandez <aldyh at gcc dot gnu.org> --- > (In reply to Richard Biener from comment #1) > > You need > > > > if (p_2(D) == _Literal (char *) &global[2]) > > > > and of course you need to provide the > > > > char global[10]; > > > > declaration. And then we still need to fix some sanity checking in the > > frontend. > > Thanks for the patch. I'll need something like it in order to write some jump > threading tests for missing MEM_REF cases. > > It would be nice if -fdump-tree-*-gimple would match what -fgimple expects, at > the least with regards to this _Literal business. Yeah, I have posted a patch but that has some testsuite fallout (meh). > BTW, the __MEM_REF output from the dumps does not work in -fgimple either. > More errors. Can you share an example? Thanks, Richard.
next prev parent reply other threads:[~2021-10-06 6:11 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-05 9:48 [Bug other/102605] New: " aldyh at gcc dot gnu.org 2021-10-05 12:16 ` [Bug other/102605] " rguenth at gcc dot gnu.org 2021-10-05 14:14 ` aldyh at gcc dot gnu.org 2021-10-05 14:37 ` cvs-commit at gcc dot gnu.org 2021-10-06 6:11 ` rguenther at suse dot de [this message] 2021-10-06 7:40 ` aldyh at redhat dot com 2021-10-06 8:13 ` rguenther at suse dot de 2021-10-06 8:28 ` aldyh at redhat dot com 2021-10-06 10:02 ` cvs-commit at gcc dot gnu.org 2021-10-07 6:21 ` 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-102605-4-fj08cBESI1@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).