Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Jason R Thorpe <thorpej@wasabisystems.com>,
	Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: HPPA multiarching plan
Date: Tue, 26 Nov 2002 07:26:00 -0000	[thread overview]
Message-ID: <3DE392B3.70205@redhat.com> (raw)
In-Reply-To: <20021126010438.GD21009@yeah-baby.shagadelic.org>

> On Mon, Nov 25, 2002 at 04:48:57PM -0800, Joel Brobecker wrote:
> 
>  >   - Add 2 new OSABI enums: HPPA_HPUX and HPPA64_HPUX.
>  >     (it seems important to me to keep the OS name in the enum, to
>  >     differentiate with HPPA_LINUX for instance)
> 
> You should not need the processor name in the OSABI ("embedded ABIs"
> are kind of a special case, which is why you see the processor name
> in those).  You also should not need the "64" .. I would guess that
> would be differentiated based on the object file format (SOM [32] vs.
> Elf32 vs. Elf64 -- assuming hppa64 binaries use the Elf64 format; I'm
> not sure that they do, please educate me :-).
> 
> So, I think you only need GDB_OSABI_HPUX.

Assuming that HPPA64 and HPPA are different ABIs (true?), then they 
should be identified using separate OSABI designations.  That way, the 
ABI code is independant of the underlying object file format (ELF or SOM 
or ....).

This is more in line with MIPS with n32, o32, o64 and 64.

Andrew



  parent reply	other threads:[~2002-11-26 15:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-25 16:48 Joel Brobecker
2002-11-25 16:58 ` Daniel Jacobowitz
2002-11-25 17:04 ` Jason R Thorpe
2002-11-25 17:24   ` Joel Brobecker
2002-11-25 17:47     ` Jason R Thorpe
2002-11-26  7:26   ` Andrew Cagney [this message]
2002-11-26  7:56     ` Jason R Thorpe

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=3DE392B3.70205@redhat.com \
    --to=ac131313@redhat.com \
    --cc=brobecker@gnat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=thorpej@wasabisystems.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