From: Martin Sebor <msebor@gmail.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, Jeff Law <law@redhat.com>
Subject: Re: [PATCH] add --param ssa-name-def-chain-limit
Date: Fri, 12 Jul 2019 17:25:00 -0000 [thread overview]
Message-ID: <797d0896-486d-60fa-3c0d-d1b36765b3ba@gmail.com> (raw)
In-Reply-To: <CAFiYyc1X_79ewEJ3qqL=aAjKb64Ea=iXsZc4crQEHnUnOJMoNg@mail.gmail.com>
On 7/12/19 3:35 AM, Richard Biener wrote:
> On Thu, Jul 11, 2019 at 7:43 PM Martin Sebor <msebor@gmail.com> wrote:
>>
>> Attached is a patch that adds a new parameter to limit the number
>> of SSA_NAME assignments for GCC to follow in iterative or recursive
>> algorithms. Purely as a proof of concept the patch introduces
>> the parameter into -Warray-bounds where the warning follows
>> POINTER_PLUS (and ASSERT_EXPR) assignments to get at the DECL
>> the final pointer points to.
>>
>> With this "infrastructure" in place the parameter can start to be
>> introduced wherever else it might be necessary. I don't know of
>> any pathological cases where it actually is necessary (i.e., one
>> the 512 default keeps from going off the rails) so the test I have
>> put together for it is artificial. A better test case involving
>> one of the known recursive algorithms would be helpful.
>
> The docs talk about diagnostics so I wonder if the param
> name should include that as well, otherwise OK.
I committed the patch as is for now. The parameter's effect is
on both, optimization and diagnostics, so a generic name seems
like a good fit. Plus, I couldn't off hand think of a better
name. We can always change it if you or someone else comes up
with one.
Martin
prev parent reply other threads:[~2019-07-12 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 18:34 Martin Sebor
2019-07-12 9:44 ` Richard Biener
2019-07-12 17:25 ` Martin Sebor [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=797d0896-486d-60fa-3c0d-d1b36765b3ba@gmail.com \
--to=msebor@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=richard.guenther@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).