public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Ilya Enkovich <enkovich.gnu@gmail.com>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [CHKP, PATCH] Fix instrumented indirect calls with propagated pointers
Date: Wed, 25 Mar 2015 10:15:00 -0000	[thread overview]
Message-ID: <CAFiYyc3TgF=FKsuL2kJqJTZESWdd7pr_O0Zu2QoWz+j-kK=-Fw@mail.gmail.com> (raw)
In-Reply-To: <20150325095041.GL1746@tucnak.redhat.com>

On Wed, Mar 25, 2015 at 10:50 AM, Jakub Jelinek <jakub@redhat.com> wrote:
> On Wed, Mar 25, 2015 at 10:38:56AM +0100, Richard Biener wrote:
>> --- gcc/passes.c        (revision 221633)
>> +++ gcc/passes.c        (working copy)
>> @@ -156,7 +156,8 @@ void
>>  pass_manager::execute_early_local_passes ()
>>  {
>>    execute_pass_list (cfun, pass_build_ssa_passes_1->sub);
>> -  execute_pass_list (cfun, pass_chkp_instrumentation_passes_1->sub);
>> +  if (flag_check_pointer_bounds)
>> +    execute_pass_list (cfun, pass_chkp_instrumentation_passes_1->sub);
>>    execute_pass_list (cfun, pass_local_optimization_passes_1->sub);
>>  }
>>
>> @@ -424,7 +425,8 @@ public:
>>    virtual bool gate (function *)
>>      {
>>        /* Don't bother doing anything if the program has errors.  */
>> -      return (!seen_error () && !in_lto_p);
>> +      return (flag_check_pointer_bounds
>> +             && !seen_error () && !in_lto_p);
>>      }
>>
>>  }; // class pass_chkp_instrumentation_passes
>
> There is still the wasteful pass_fixup_cfg at the start of:
> PUSH_INSERT_PASSES_WITHIN (pass_local_optimization_passes)
>   NEXT_PASS (pass_fixup_cfg);
> which wasn't there before chkp.  Perhaps this should be a different
> pass with the same execute method, but gate containing
> flag_check_pointer_bounds?

That's not wasteful but required due to local_pure_const.  The remaining
wasteful fixup_cfg is the one in pass_build_ssa_passes.  ISTR
that pass_ipa_chkp_versioning/early_produce_thunks makes that one
required?  Or EH / CFG cleanup stuff makes it necessary to not
fail IL checking done by into-SSA.

Richard.

>         Jakub

  parent reply	other threads:[~2015-03-25 10:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-12 11:13 Ilya Enkovich
2015-03-19  8:30 ` Ilya Enkovich
2015-03-24  8:33   ` Jakub Jelinek
2015-03-24  9:22     ` Ilya Enkovich
2015-03-24 14:06       ` Jakub Jelinek
2015-03-24 14:40         ` Richard Biener
2015-03-25  8:50           ` Ilya Enkovich
2015-03-25  9:39             ` Richard Biener
2015-03-25  9:50               ` Jakub Jelinek
2015-03-25 10:06                 ` Ilya Enkovich
2015-03-25 10:11                   ` Jakub Jelinek
2015-03-25 10:20                     ` Richard Biener
2015-03-25 10:15                 ` Richard Biener [this message]
2015-03-25 10:24                   ` Ilya Enkovich
2015-03-25  8:05         ` Ilya Enkovich
2015-03-25  8:16           ` Jakub Jelinek
2015-03-25  8:56             ` Ilya Enkovich
2015-04-02 16:28         ` Ilya Enkovich
2015-04-10  1:28           ` Jan Hubicka
2015-04-14 14:35             ` Ilya Enkovich
2015-05-05  8:06               ` Ilya Enkovich
2015-05-19  9:40                 ` Ilya Enkovich
2015-05-26 13:11                   ` Ilya Enkovich
2015-05-29  6:49                     ` Jan Hubicka

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='CAFiYyc3TgF=FKsuL2kJqJTZESWdd7pr_O0Zu2QoWz+j-kK=-Fw@mail.gmail.com' \
    --to=richard.guenther@gmail.com \
    --cc=enkovich.gnu@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.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).