mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [PATCH 2/3] fix matching errors related to i386 addressing modes in CFI generation script
Date: Mon, 12 Oct 2015 11:12:03 -0400	[thread overview]
Message-ID: <20151012151203.GO8645@brightrain.aerifal.cx> (raw)
In-Reply-To: <1444658340-10065-2-git-send-email-alexinbeijing@gmail.com>

On Mon, Oct 12, 2015 at 03:58:59PM +0200, Alex Dowad wrote:
> the regexps previously used to identify registers clobbered by MOVs, ADDs,
> and various other operations would erroneously match index registers. In other
> words, the following asm:
> 
>     mov $0, (%eax,%ebx,4)
> 
> ....would cause EBX to be considered as overwritten, which might prevent a
> debugger from displaying a variable's value in a higher stack frame.
> 
> thanks to Rich Felker for noticing this problem.
> ---
>  tools/add-cfi.i386.awk | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/tools/add-cfi.i386.awk b/tools/add-cfi.i386.awk
> index fc0d8cf..bd7932f 100644
> --- a/tools/add-cfi.i386.awk
> +++ b/tools/add-cfi.i386.awk
> @@ -184,13 +184,13 @@ function trashed(register) {
>  }
>  # this does NOT exhaustively check for all possible instructions which could
>  # overwrite a register value inherited from the caller (just the common ones)
> -/mov.*,%e(ax|bx|cx|dx|si|di|bp)/  { trashed(get_reg2()) }
> -/(add|addl|sub|subl|and|or|xor|lea|sal|sar|shl|shr).*,%e(ax|bx|cx|dx|si|di|bp)/ {
> +/mov.*,%e(ax|bx|cx|dx|si|di|bp)$/  { trashed(get_reg2()) }
> +/(add|addl|sub|subl|and|or|xor|lea|sal|sar|shl|shr).*,%e(ax|bx|cx|dx|si|di|bp)$/ {
>    trashed(get_reg2())
>  }
> -/^i?mul [^,]*$/                     { trashed("eax"); trashed("edx") }
> -/^i?mul.*,%e(ax|bx|cx|dx|si|di|bp)/ { trashed(get_reg2()) }
> -/^i?div/                            { trashed("eax"); trashed("edx") }
> +/^i?mul [^,]*$/                      { trashed("eax"); trashed("edx") }
> +/^i?mul.*,%e(ax|bx|cx|dx|si|di|bp)$/ { trashed(get_reg2()) }
> +/^i?div/                             { trashed("eax"); trashed("edx") }
>  /(dec|inc|not|neg|pop) %e(ax|bx|cx|dx|si|di|bp)/  { trashed(get_reg()) }
>  /cpuid/ { trashed("eax"); trashed("ebx"); trashed("ecx"); trashed("edx") }

Clever. At first I didn't see how this was fixing anything, with the
.* still there, but given that you strip comments and extra
whitespace, anchoring to the end with $ seems to work.

While seeing them separately was useful for seeing how you fixed the
bug, patches 1 and 2 should be merged for commit. All patch 2 is doing
is fixing a bug that patch 1 introduces; together they just form a
non-buggy version of "fix operand order". I can take care of the
merging though.

One other thing I noticed for future improvement: your patterns don't
seem to catch instructions that modify just the low byte or half of a
register. These are fairly uncommon in musl's i386 asm, but for
x86_64, I would estimate a good 50% of register usage uses the 32-bit
half (%e..) of a register rather than the full %r.., and your current
script fails to mark these clobbers at all. Probably the regex should
be something like %[er]?([abcd][xlh]|si|di|bp|...) - I don't recall
the right form for the numbered x86_64 registers' low parts right off,
though.

Rich


  reply	other threads:[~2015-10-12 15:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-12 13:58 [PATCH 1/3] in i386 CFI script, binary ops like ADD or AND modify 2nd operand, not 1st Alex Dowad
2015-10-12 13:58 ` [PATCH 2/3] fix matching errors related to i386 addressing modes in CFI generation script Alex Dowad
2015-10-12 15:12   ` Rich Felker [this message]
2015-10-12 18:30     ` Alex
2015-10-12 13:59 ` [PATCH 3/3] add CFI generation script for x86_64 Alex Dowad

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=20151012151203.GO8645@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).