Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [patch] Support bionic's jmp_buf.
Date: Wed, 27 Jun 2012 10:18:00 -0000	[thread overview]
Message-ID: <4FEADDDE.6020904@redhat.com> (raw)
In-Reply-To: <1340574375.31308.7.camel@hactar>

On 06/24/2012 10:46 PM, Thiago Jung Bauermann wrote:>>> Urgh.  Isn't there a better way?  This doesn't work with shared libraries,
>>> > > for starters.
>> >
>> > There is. I thought of adding an Android flag to .note.ABI-tag and I
>> > even have a patch ready which adds it to Android  binaries. I gave up on
>> > it because I thought it was overkill but I can certainly use that if
>> > using the interpreter field is a worse solution.
> I submitted a patch to bionic which adds a .note.ABI-tag to Android
> binaries:
>
> https://android-review.googlesource.com/37590
> The note has a flag which is set to 1 if the binary is for the Android
> platform.
> 
> The patch was accepted by the Google engineers and applied to their
> internal tree. It wasn't merged yet to the AOSP tree because of
> conflicts with some of their internal patches, but will be in the near
> future.

Thank you very much for persevering.  I think that using "GNU" as
ABI_VENDOR for Android isn't the best thing to do, but from skimming
the binutils@ list I see you're already addressing that.

-- 
Pedro Alves


  parent reply	other threads:[~2012-06-27 10:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-21  0:36 Thiago Jung Bauermann
2012-05-21 11:38 ` Pedro Alves
2012-05-21 17:59   ` Thiago Jung Bauermann
2012-06-24 21:46     ` Thiago Jung Bauermann
2012-06-25 13:32       ` Yao Qi
2012-06-25 17:55         ` Thiago Jung Bauermann
2012-06-25 20:49           ` Schnell, Fabian
2012-06-27 10:18       ` Pedro Alves [this message]
2012-07-04 21:08         ` Thiago Jung Bauermann

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=4FEADDDE.6020904@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=thiago.bauermann@linaro.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