This is the mail archive of the mailing list for the binutils project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: [PATCH 1/2] Add support for O32 FPXX ABI

Joseph Myers <> writes:
> On Mon, 7 Apr 2014, Matthew Fortune wrote:
> > > What did you think about the idea of reusing the .gnu_attributes
> > > section data as the segment data?  It seems simpler than the PT_NOTE
> format.
> >
> > I have no major objection. Slight concern over defining more of the
> > MIPS ABI around the 'gnu' vendor attributes which is a bit strange
> > given the MIPS architecture is not restricted to gnu tools. Having
> > said that, MIPS is already using these as critical parts of the ABI
> > and following it through to load time information as well then seems
> reasonable.
> >
> > In order to use the pre-existing section for GNU attributes I guess it
> > would need to become SEC_ALLOC and get associated with the new program
> > header. Perhaps call it PT_MIPS_ATTRIBUTES or PT_GNU_ATTRIBUTES if
> > this were done for all architectures. And then somehow get that to be
> > positioned immediately after the notes segment.
> Making an allocated segment for attributes was previously rejected; see
> references in <>.  I
> don't think anything significant has changed to affect that design
> principle.

Later in this thread Richard and I essentially re-did that entire discussion
and also rejected making an allocated attributes segment. The current plan
is to add a new section with a new segment/program header for MIPS ABI
flags. I'm calling it .MIPS.abiflags, at least for now, and this section
contains a versioned structure including various useful data about what
the binary is. I'm getting close to a patch to send for initial comments.

dl-load.c in glibc will need an extra hook adding to allow a port to act
upon custom program headers and read extra data from the DSO. The new
segment will be close to the program headers but may well be outside of
the statically determined size that dl-open reads to start with.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]