From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12355 invoked by alias); 26 Nov 2002 00:48:58 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 12348 invoked from network); 26 Nov 2002 00:48:57 -0000 Received: from unknown (HELO takamaka.act-europe.fr) (142.179.108.108) by sources.redhat.com with SMTP; 26 Nov 2002 00:48:57 -0000 Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 69EC6D2CE5; Mon, 25 Nov 2002 16:48:57 -0800 (PST) Date: Mon, 25 Nov 2002 16:48:00 -0000 From: Joel Brobecker To: gdb-patches@sources.redhat.com Subject: HPPA multiarching plan Message-ID: <20021126004857.GB23000@gnat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-SW-Source: 2002-11/txt/msg00623.txt.bz2 [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