From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Cc: hjl.tools@gmail.com, jan.kratochvil@redhat.com
Subject: Re: [PATCH] gdb: x86: fix x32 builds with inline asm
Date: Tue, 08 Jan 2013 15:57:00 -0000 [thread overview]
Message-ID: <201301081059.40723.vapier@gentoo.org> (raw)
In-Reply-To: <1357657280-24150-1-git-send-email-vapier@gentoo.org>
[-- Attachment #1: Type: Text/Plain, Size: 1232 bytes --]
On Tuesday 08 January 2013 10:01:20 Mike Frysinger wrote:
> -#if defined __i386__
> - asm volatile ("pushl %0;"
> - ".globl linux_ptrace_test_ret_to_nx_instr;"
> - "linux_ptrace_test_ret_to_nx_instr:"
> - "ret"
> - : : "r" (return_address) : "%esp", "memory");
> -#elif defined __x86_64__
> - asm volatile ("pushq %0;"
> + asm volatile ("push %0;"
> ".globl linux_ptrace_test_ret_to_nx_instr;"
> "linux_ptrace_test_ret_to_nx_instr:"
> "ret"
> - : : "r" (return_address) : "%rsp", "memory");
> -#else
> -# error "!__i386__ && !__x86_64__"
> -#endif
> + : : "r" (return_address) : "sp", "memory");
hrm, this works for -m32 and -m64, but doesn't actually help with -mx32. this
doesn't seem to line up with my expectations. can you suggest something here
H.J. Lu ?
$ cat test.c
main() { asm volatile ("push %0; ret;" : : "r"(main) : "sp", "memory"); }
$ gcc -m32 test.c
8: 50 push %eax
9: c3 ret
$ gcc -m64 test.c
9: 50 push %rax
a: c3 retq
$ gcc -mx32 test.c
test.c: Assembler messages:
test.c:2: Error: operand type mismatch for `push'
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-01-08 15:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 14:59 Mike Frysinger
2013-01-08 15:36 ` H.J. Lu
2013-01-08 15:50 ` Mike Frysinger
2013-01-08 17:22 ` Jan Kratochvil
2013-01-08 15:57 ` Mike Frysinger [this message]
2013-01-08 16:54 ` H.J. Lu
2013-01-08 17:42 ` Mike Frysinger
2013-01-08 17:50 ` H.J. Lu
2013-01-08 18:42 ` [PATCH v2] " Mike Frysinger
2013-01-08 18:52 ` Jan Kratochvil
2013-01-08 19:18 ` Mike Frysinger
2013-01-08 19:53 ` Jan Kratochvil
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=201301081059.40723.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=jan.kratochvil@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