This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: Link with mixed IR/non-IR objects
- From: Markus Trippelsdorf <markus at trippelsdorf dot de>
- To: "H.J." <hjl dot tools at gmail dot com>
- Cc: Generic System V Application Binary Interface <generic-abi at googlegroups dot com>, binutils at sourceware dot org
- Date: Wed, 27 Apr 2011 16:29:09 +0200
- Subject: Re: Link with mixed IR/non-IR objects
- References: <b7c06571-1614-49af-ab54-2061c2bfbf91@l2g2000prg.googlegroups.com>
On 2011.04.27 at 06:49 -0700, H.J. wrote:
> Here is a proposal to link with mixed IR/non-IR objects:
>
> * 2 kinds of object files
> o non-IR object file has
> * non-IR sections
> o IR object file has
> * IR sections
> * non-IR sections
> * The output of "ld -r" with mixed IR/non-IR objects should work
> with:
> o Compilers/linkers with IR support.
> o Compilers/linkers without IR support.
> * Add the mixed object file which has
> o IR sections
> o non-IR sections:
> * Object codes from IR sections.
> * Object codes from non-IR object files.
> o Object-only section:
> * With section name ".gnu_object_only" and SHT_GNU_OBJECT_ONLY
> type
> on ELF:
> #define SHT_GNU_OBJECT_ONLY 0x6ffffff8 /* Object only */
I'm wondering if it wouldn't be better to simply use:
SHT_GNU_IRBITS (= 0x6fff4952)
that has already been proposed here:
http://gcc.gnu.org/wiki/whopr/driver ?
»Thus, we plan to mark the IR sections with a special section type,
SHT_GNU_IRBITS (= 0x6fff4952).«
--
Markus