From: Jeff Law <law@redhat.com>
To: Martin Sebor <msebor@gmail.com>,
JiangNing OS <jiangning@os.amperecomputing.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] PR91195: fix -Wmaybe-uninitialized warning for conditional store optimization
Date: Fri, 26 Jul 2019 05:07:00 -0000 [thread overview]
Message-ID: <276f0d65-6af7-13be-769f-930e5df91d99@redhat.com> (raw)
In-Reply-To: <0f07b57e-9def-2758-c58b-ec9200fa4432@gmail.com>
On 7/24/19 12:07 PM, Martin Sebor wrote:
>
> I don't know what Jakub had in mind but the mapping I envision is
> one like hash_map<tree, bitmap> that would make it possible to set
> a bit for each distinct warning for every tree node. It would let
> us set a bit for -Wuninitialized while leaving the bit for
> -Warray-bounds (and all other warnings) clear.
Ah, yes. I like that. I'm still worried about the linkage between the
map and the GC system, but a <tree, bitmap> has a lot of potential.
>
>>
>> If the bit were on an SSA_NAME, or a _DECL node, then the flag bit is
>> shared and would be a much larger concern.
>
> For shared objects the mapping would have to be more involved but
> I haven't thought about it in any detail to have an idea what it
> might look like.
I suspect shared objects are just going to be painful. A solution which
worked on EXPR nodes would still be a significant step forward.
>
> Anyway, if/when someone does come up with a solution for this we
> will have to go through all the places where the no-warning bit
> is set and replace them with whatever replacement we come up with.
> One instance more or less won't make a difference. I just wanted
> to point out that setting the bit is not a robust solution.
Yea, but at least they're easy to find via the TREE_NO_WARNING flag.
Hopefully we've got tests for most of the issues we're working around
with that bit.
jeff
next prev parent reply other threads:[~2019-07-26 4:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 5:52 JiangNing OS
2019-07-23 16:31 ` Martin Sebor
2019-07-24 15:28 ` Jeff Law
2019-07-24 17:00 ` Martin Sebor
2019-07-24 17:23 ` Jeff Law
2019-07-24 18:09 ` Martin Sebor
2019-07-25 6:27 ` JiangNing OS
2019-07-25 19:09 ` Martin Sebor
2019-07-26 5:07 ` Jeff Law [this message]
2019-07-29 16:10 ` Jakub Jelinek
2019-07-30 8:35 ` Richard Biener
2019-07-30 8:36 ` Jakub Jelinek
2019-07-30 8:49 ` Richard Biener
2019-07-30 14:51 ` Martin Sebor
2019-08-07 22:17 ` Jeff Law
2019-09-03 20:22 ` Jeff Law
2019-07-24 16:00 ` Jeff Law
2019-07-29 16:03 ` Jakub Jelinek
2019-09-03 20:27 ` Jeff Law
2019-11-20 0:14 ` Jakub Jelinek
2019-11-20 2:33 ` Jeff Law
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=276f0d65-6af7-13be-769f-930e5df91d99@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jiangning@os.amperecomputing.com \
--cc=msebor@gmail.com \
/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).