public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@gmail.com>
To: Andreas Schwab <schwab@redhat.com>
Cc: libc-hacker@sourceware.org
Subject: Re: [PATCH] Maintain stack alignment in ____longjmp_chk on x86_64
Date: Thu, 07 Apr 2011 13:29:00 -0000	[thread overview]
Message-ID: <BANLkTi=Knz1pQ+EEJL_4wx+RCbAodfO9yA@mail.gmail.com> (raw)
In-Reply-To: <m3oc4ib5x5.fsf@redhat.com>

On Thu, Apr 7, 2011 at 08:29, Andreas Schwab <schwab@redhat.com> wrote:
> +                       call    __GI___fortify_fail;                          \
> +                       nop;                                                  \

Why would we need the nop after the call?  This isn't SPARC...

  reply	other threads:[~2011-04-07 13:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-07 12:30 Andreas Schwab
2011-04-07 13:29 ` Ulrich Drepper [this message]
2011-04-07 13:39   ` Andreas Schwab

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='BANLkTi=Knz1pQ+EEJL_4wx+RCbAodfO9yA@mail.gmail.com' \
    --to=drepper@gmail.com \
    --cc=libc-hacker@sourceware.org \
    --cc=schwab@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).