public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bernd Schmidt <bschmidt@redhat.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Uros Bizjak <ubizjak@gmail.com>
Subject: Re: regrename/i386: ROP vs df and stack-regs
Date: Mon, 30 Nov 2015 21:47:00 -0000	[thread overview]
Message-ID: <565CC1DC.2000508@redhat.com> (raw)
In-Reply-To: <56581C2F.9070300@redhat.com>

On 11/27/2015 10:02 AM, Bernd Schmidt wrote:
> This is a patch for PRs 68471 and 68472, which show problems with the
> ROP mitigation:
>   * reg-stack doesn't call df_insn_update when it makes changes, and
>     if df checking is enabled, any subsequent df_analyze call will
>     abort
>   * Using -mcmodel=medium fails because of a pattern that has lea type
>     and needs its modrm_class overridden.
>
> Both of these are fixed in the i386 backend. As a further safety
> measure, I've added some extra code to regrename to ignore stack regs
> after regstack_complete - they can't be dealt with anymore.
>
> Bootstrapped and tested on x86_64-linux, with -mmitigate-rop forced on. Ok?

> 	PR target/68471
> 	PR target/68472
> 	* config/i386/i386.c (ix86_mitigate_rop): Don't call
> 	compute_bb_for_insn again.  Call df_insn_rescan_all.
> 	* config/i386/i386.md (set_got_rex64): Override modrm_class.
>
> 	* regrename.c (build_def_use): Ignore stack regs if regstack_completed.
>
> testsuite/
> 	* gcc.target/i386/rop1.c: New test.
>
> diff --git a/gcc/config/i386/i386.c b/gcc/config/i386/i386.c
> index 2ac6c25..14c99eb 100644
> --- a/gcc/config/i386/i386.c
> +++ b/gcc/config/i386/i386.c
> @@ -45243,8 +45243,9 @@ ix86_mitigate_rop (void)
>    COPY_HARD_REG_SET (inout_risky, input_risky);
>    IOR_HARD_REG_SET (inout_risky, output_risky);
>
> -  compute_bb_for_insn ();
>    df_note_add_problem ();
> +  /* Fix up what stack-regs did.  */
> +  df_insn_rescan_all ();
>    df_analyze ();
>
>    regrename_init (true);
> diff --git a/gcc/config/i386/i386.md b/gcc/config/i386/i386.md
> index a57d165..671580d 100644
> --- a/gcc/config/i386/i386.md
> +++ b/gcc/config/i386/i386.md
> @@ -12418,6 +12418,7 @@
>    "lea{q}\t{_GLOBAL_OFFSET_TABLE_(%%rip), %0|%0, _GLOBAL_OFFSET_TABLE_[rip]}"
>    [(set_attr "type" "lea")
>     (set_attr "length_address" "4")
> +   (set_attr "modrm_class" "unknown")
>     (set_attr "mode" "DI")])
>
>  (define_insn "set_rip_rex64"
> --- /dev/null	2015-11-23 12:05:22.553607702 +0100
> +++ gcc/testsuite/gcc.target/i386/rop1.c	2015-11-24 15:40:04.381086953 +0100
> @@ -0,0 +1,7 @@
> +/* { dg-do compile } */
> +/* { dg-require-effective-target lp64 } */
> +/* { dg-options "-mcmodel=medium -mmitigate-rop" } */
> +void
> +foo (void)
> +{
> +}

Ccing Uros for the i386 bits.


Bernd

  parent reply	other threads:[~2015-11-30 21:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-27  9:21 Bernd Schmidt
2015-11-27  9:30 ` Eric Botcazou
2015-11-27  9:36   ` Bernd Schmidt
2015-11-27  9:45     ` Eric Botcazou
2015-11-30 21:47 ` Bernd Schmidt [this message]
2015-11-30 22:06   ` Uros Bizjak

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=565CC1DC.2000508@redhat.com \
    --to=bschmidt@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ubizjak@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).