public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rth at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nptl/17165] [alpha] Saved stack pointer is not mangled in unwind_stop jumpbuffer
Date: Wed, 30 Jul 2014 05:21:00 -0000	[thread overview]
Message-ID: <bug-17165-131-rXCX6FdoW7@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17165-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=17165

Richard Henderson <rth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING
                 CC|                            |rth at gcc dot gnu.org

--- Comment #3 from Richard Henderson <rth at gcc dot gnu.org> ---
I don't see this problem with mainline glibc, although I admit I
compiled for ev67, not ev4.  I just wouldn't have thought that
would make any difference.

$ ./elf/ld.so --library-path .:elf:math:nptl ~/a.out
unwind

0000000000000000 <__sigsetjmp>:
   0:   00 00 bb 27     ldah    gp,0(t12)
                        0: GPDISP       .text+0x4
   4:   00 00 bd 23     lda     gp,0(gp)
   8:   00 00 30 b5     stq     s0,0(a0)
   c:   08 00 50 b5     stq     s1,8(a0)
  10:   10 00 70 b5     stq     s2,16(a0)
  14:   18 00 90 b5     stq     s3,24(a0)
  18:   20 00 b0 b5     stq     s4,32(a0)
  1c:   28 00 d0 b5     stq     s5,40(a0)
  20:   00 00 3d a4     ldq     t0,0(gp)
                        20: ELF_LITERAL __pointer_chk_guard
  24:   00 00 21 a4     ldq     t0,0(t0)
                        24: LITUSE      .text+0x1
  28:   02 08 41 47     xor     ra,t0,t1
  2c:   30 00 50 b4     stq     t1,48(a0)
  30:   02 08 c1 47     xor     sp,t0,t1
  34:   40 00 50 b4     stq     t1,64(a0)
  38:   02 08 e1 45     xor     fp,t0,t1
  3c:   38 00 50 b4     stq     t1,56(a0)

Can you please re-verify mainline?  We're going to cut 2.20 soon.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2014-07-30  5:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-16 16:17 [Bug nptl/17165] New: " ubizjak at gmail dot com
2014-07-16 16:39 ` [Bug nptl/17165] " ubizjak at gmail dot com
2014-07-16 17:16 ` ubizjak at gmail dot com
2014-07-30  5:21 ` rth at gcc dot gnu.org [this message]
2014-07-30  6:36 ` ubizjak at gmail dot com
2014-07-30  7:48 ` ubizjak at gmail dot com
2014-07-30 17:17 ` rth at gcc dot gnu.org

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=bug-17165-131-rXCX6FdoW7@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /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).