Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@gnat.com>
To: gdb-patches@sources.redhat.com
Subject: HPPA multiarching plan
Date: Mon, 25 Nov 2002 16:48:00 -0000	[thread overview]
Message-ID: <20021126004857.GB23000@gnat.com> (raw)

[This plan assumes that the ports to bsd/osf/pro are either obsoleted, or
taken care of by somebody else]

today I have tried to get a bigger picture of what to do to get the hppa
ports (partially) multi-arched. The targets that I will be converting
are:
	hppa*64*-*-hpux11*
	hppa*-*-hpux*
	hppa*-*-hiux*

I am assuming hiux is just a synonym of hpux?

The first thing I wasn't sure was to build an os_abi sniffer. So far,
given the short lists of targets, I suggest the following:

  - 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)

  - The sniffer would then guess the correct value based like so:

    1. If object format is ELF
       -> OSABI = HPPA64_HPUX

    2. If object format is SOM
       -> OSABI = HPPA_HPUX
      
    Later on, when we want to add support for hppa-linux, the sniffer will
    need to be refined. I assume hppa-linux uses ELF? In which case we
    will probably have to dig into the ELF header to search for the clue
    that will reveal either hpux or linux.

What do you think?

-- 
Joel


             reply	other threads:[~2002-11-26  0:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-25 16:48 Joel Brobecker [this message]
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
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=20021126004857.GB23000@gnat.com \
    --to=brobecker@gnat.com \
    --cc=gdb-patches@sources.redhat.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