public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Matthew Fortune <Matthew.Fortune@imgtec.com>
To: "Maciej W. Rozycki" <macro@codesourcery.com>
Cc: Roland McGrath <roland@hack.frob.com>,
	Richard Sandiford	<rdsandiford@googlemail.com>,
	"binutils@sourceware.org"	<binutils@sourceware.org>,
	"libc-alpha@sourceware.org"	<libc-alpha@sourceware.org>,
	"gdb@sourceware.org" <gdb@sourceware.org>,
	"Joseph Myers (joseph@codesourcery.com)"
	<joseph@codesourcery.com>,
	"Moore,
	Catherine (Catherine_Moore@mentor.com)"
	<Catherine_Moore@mentor.com>,
	Nikola Veljkovic <Nikola.Veljkovic@imgtec.com>
Subject: RE: [RFC][MIPS] What to do about DT_MIPS_RLD_MAP and PIE
Date: Fri, 14 Nov 2014 11:27:00 -0000	[thread overview]
Message-ID: <6D39441BF12EF246A7ABCE6654B0235320F7015D@LEMAIL01.le.imgtec.org> (raw)
In-Reply-To: <alpine.DEB.1.10.1411131754290.2881@tp.orcam.me.uk>

> On Thu, 13 Nov 2014, Matthew Fortune wrote:
> 
> > OK, unless anyone objects I will prepare patches on that basis.
> >
> > It looks like there are no GNU tags defined yet in the 'new'
> > OS range for tags. Should I just take the first one?
> >
> > #define DT_GNU_RLD_MAP 0x6000000d
> 
>  That would be the natural choice in my opinion unless someone already
> uses it for something in a private tree or branch and did not mention it
> so far, but plans to submit their code.  I think we shouldn't be causing
> hassle to anyone unnecessarily.  Do we have a place (other than the
> relevant pieces of source code) we use to document our (GNU) ABI
> conventions?

One concern is over what the GNU ABI encompasses. I.e. We have glibc, uclibc
musl and bionic (that I know of) which provide dynamic linker functionality
with the linux kernel. If they are independently allowed to define tags then
there is a high chance of collision and bugs from accidentally getting a linker
to target the wrong 'OS'.

So do we have to take the 'GNU' OS to mean anything which provides dynamic
linking on linux? Is there already a description of what it means and/or can
someone think of a sensible description?

In some ways doing this as an architecture independent extension may actually
require specifying it in the ELF ABI itself.

Thanks,
Matthew

      parent reply	other threads:[~2014-11-14 11:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6D39441BF12EF246A7ABCE6654B0235320F3027E@LEMAIL01.le.imgtec.org>
     [not found] ` <alpine.DEB.1.10.1410221755430.7896@tp.orcam.me.uk>
     [not found]   ` <6D39441BF12EF246A7ABCE6654B0235320F30462@LEMAIL01.le.imgtec.org>
     [not found]     ` <871tpy37ir.fsf@googlemail.com>
     [not found]       ` <6D39441BF12EF246A7ABCE6654B0235320F385FA@LEMAIL01.le.imgtec.org>
     [not found]         ` <alpine.DEB.1.10.1410301835480.7896@tp.orcam.me.uk>
     [not found]           ` <20141030193816.E80F82C3B18@topped-with-meat.com>
2014-10-30 23:53             ` Maciej W. Rozycki
2014-11-04 11:14               ` Matthew Fortune
2014-11-12 23:11                 ` Matthew Fortune
2014-11-12 23:32                   ` Roland McGrath
2014-11-13 16:37                     ` Matthew Fortune
2014-11-13 18:00                       ` Maciej W. Rozycki
2014-11-13 19:10                         ` Roland McGrath
2014-11-14 11:27                         ` Matthew Fortune [this message]

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=6D39441BF12EF246A7ABCE6654B0235320F7015D@LEMAIL01.le.imgtec.org \
    --to=matthew.fortune@imgtec.com \
    --cc=Catherine_Moore@mentor.com \
    --cc=Nikola.Veljkovic@imgtec.com \
    --cc=binutils@sourceware.org \
    --cc=gdb@sourceware.org \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=macro@codesourcery.com \
    --cc=rdsandiford@googlemail.com \
    --cc=roland@hack.frob.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).