From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-14252-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 8644 invoked by alias); 12 Jun 2003 14:50:19 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 8636 invoked from network); 12 Jun 2003 14:50:19 -0000
Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76)
  by sources.redhat.com with SMTP; 12 Jun 2003 14:50:19 -0000
Received: from smtp.ott.qnx.com (smtp.ott.qnx.com [10.0.2.158])
	by hub.ott.qnx.com (8.9.3p2/8.9.3) with ESMTP id KAA01697;
	Thu, 12 Jun 2003 10:44:09 -0400
Received: from catdog ([10.4.2.2]) by smtp.ott.qnx.com (8.8.8/8.6.12) with SMTP id KAA30781; Thu, 12 Jun 2003 10:50:18 -0400
Message-ID: <015d01c330f1$fada2dc0$0202040a@catdog>
From: "Kris Warkentin" <kewarken@qnx.com>
To: "Kris Warkentin" <kewarken@qnx.com>, <Richard.Earnshaw@arm.com>
Cc: <Richard.Earnshaw@arm.com>,
        "Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>
References: <200306121427.h5CERJR20619@pc960.cambridge.arm.com> <014101c330f1$748af060$0202040a@catdog>
Subject: Re: Elf OS ABI Number 
Date: Thu, 12 Jun 2003 14:50:00 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-SW-Source: 2003-06/txt/msg00205.txt.bz2

> > Is there a good reason why you've invented your own relocs?  If the
> > processor vendor (who generally own the reloc space allocation for their
> > processor) where to allocate a reloc that conflicts with your usage at a
> > later date you might have a major problem on your hands.
>
> We do some weird stuff for execute in place and various kernel stuff.  I
> don't understand the details particularily well but we have to use our own
> linker on certain startup code and such.  Probably doesn't affect much
else.

I forgot to mention, the one place where we might legitimately need an OSABI
number is in MIPS.  We have our own ABI that doesn't force us to compile
everything PIC.  There was a whitepaper posted to binutils and gcc once upon
a time but no one was interested in it.

cheers,

Kris