public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/15407] Partial frame info in sysdeps/x86_64/start.S
Date: Tue, 30 Apr 2013 15:45:00 -0000	[thread overview]
Message-ID: <bug-15407-131-nGzqISBPc5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15407-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=15407

--- Comment #14 from H.J. Lu <hjl.tools at gmail dot com> 2013-04-30 15:45:49 UTC ---
(In reply to comment #13)
> I think the markers like __EH_FRAME_BEGIN__ could be moved from crtbegin.o to
> some new crtbegin1.o linking it then in the order:
> 
> /usr/lib/gcc/x86_64-redhat-linux/4.7.2/crtbegin1.o
> /usr/lib/gcc/x86_64-redhat-linux/4.7.2/../../../../lib64/crt1.o
> /usr/lib/gcc/x86_64-redhat-linux/4.7.2/../../../../lib64/crti.o
> /usr/lib/gcc/x86_64-redhat-linux/4.7.2/crtbegin.o
> 
> I will try to code it in GCC, I hope there is an agreement for it.

I don't know if it works for gold.  Or we can use --eh-frame-hdr
for static executables:

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54568

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2013-04-30 15:45 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-26 17:20 [Bug libc/15407] New: " hjl.tools at gmail dot com
2013-04-26 17:21 ` [Bug libc/15407] " hjl.tools at gmail dot com
2013-04-26 19:20 ` hjl.tools at gmail dot com
2013-04-26 19:28 ` hjl.tools at gmail dot com
2013-04-26 19:32 ` jan.kratochvil at redhat dot com
2013-04-26 19:40 ` jakub at redhat dot com
2013-04-26 21:22 ` roland at gnu dot org
2013-04-26 21:30 ` hjl.tools at gmail dot com
2013-04-26 21:35 ` roland at gnu dot org
2013-04-26 21:58 ` hjl.tools at gmail dot com
2013-04-26 22:17 ` roland at gnu dot org
2013-04-27 16:31 ` jan.kratochvil at redhat dot com
2013-04-29 16:11 ` hjl.tools at gmail dot com
2013-04-29 16:53 ` hjl.tools at gmail dot com
2013-04-29 22:17 ` allan at archlinux dot org
2013-04-30 15:36 ` jan.kratochvil at redhat dot com
2013-04-30 15:45 ` hjl.tools at gmail dot com [this message]
2013-05-05 18:40 ` jan.kratochvil at redhat dot com
2013-05-06 17:23 ` jan.kratochvil at redhat dot com
2013-05-09 15:26 ` hjl.tools at gmail dot com
2013-05-10 16:33 ` jan.kratochvil at redhat dot com
2013-05-10 16:59 ` hjl.tools at gmail dot com
2013-05-10 17:12 ` jan.kratochvil at redhat dot com
2013-05-10 17:22 ` hjl.tools at gmail dot com
2013-05-10 17:32 ` jan.kratochvil at redhat dot com
2013-05-10 17:45 ` hjl.tools at gmail dot com
2013-05-10 18:26 ` jan.kratochvil at redhat dot com
2013-05-10 20:33 ` hjl.tools at gmail dot com
2013-05-11  5:27 ` jan.kratochvil at redhat dot com
2014-02-07  2:45 ` [Bug libc/15407] [x86_64] " jsm28 at gcc dot gnu.org
2014-06-13 18:14 ` fweimer at redhat dot com

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-15407-131-nGzqISBPc5@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).