Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: gdb-patches@sourceware.org, jan.kratochvil@redhat.com
Subject: Re: [PATCH] gdb: x86: fix x32 builds with inline asm
Date: Tue, 08 Jan 2013 15:50:00 -0000	[thread overview]
Message-ID: <201301081052.36180.vapier@gentoo.org> (raw)
In-Reply-To: <CAMe9rOpWGMKQ+QqD8ucfv3Z2wh+fyJ7aaRomewDWzE78pJTTwQ@mail.gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 1610 bytes --]

On Tuesday 08 January 2013 10:36:11 H.J. Lu wrote:
> On Tue, Jan 8, 2013 at 7:01 AM, Mike Frysinger wrote:
> > --- a/gdb/common/linux-ptrace.c
> > +++ b/gdb/common/linux-ptrace.c
> > @@ -103,21 +103,11 @@ linux_ptrace_test_ret_to_nx (void)
> >                  strerror (errno));
> >        else
> >         {
> > -#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");
> >           gdb_assert_not_reached ("asm block did not terminate");
> >         }
> 
> I think we should keep
> 
> #else
> # error "!__i386__ && !__x86_64__"
> #endif

that #else case is currently impossible to hit because the whole func is 
protected by:
#if defined __i386__ || defined __x86_64__

i'm guessing the #else was there only to make sure that some asm test was 
performed, but since there is no conditional asm, that's no longer an issue
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-01-08 15:50 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 [this message]
2013-01-08 17:22     ` Jan Kratochvil
2013-01-08 15:57 ` Mike Frysinger
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=201301081052.36180.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