This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC 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: 3.2 PATCH: Support O32 ABI on IRIX 6


> I'd like to get this initial cut at IRIX 6 O32 support in now since it
> doesn't affect existing configurations and post followup patches to address
> testsuite failures.

The patches themselves look fine, as long as we're thinking that we'll
still need to have a separate compiler for the o32 bits. I'd like the
CPP_PREDEFINES/SUBTARGET_CPP_SPEC etc, stuff removed, but in general
they are fine. I was wondering more on your thoughts as to this approach
as opposed to attempting to support o32/n32/n64 on irix6. I believe more
of the mechanisms may be there now than there were in the past and this
should make it easier.

> This section is created by mips.c (mips_asm_file_start) [TARGET_GAS &&
> OBJECT_FORMAT_ELF].  Contrary to the comment there, current gdb or bfd
> don't seem to need or use this information, so it may well be possible to
> get rid of this code completely, unless there are other known uses.
> 

I added this code when I was adding the mips32/mips64 compiler bits in
as a separate way of determining ABI since we had/were running out of
bits. It was due to have separate code in gdb that I should _really_
resurrect, but wasn't multi-arched at the time. Kind of an odd warning
though since I don't get that normally. We could probably conditionalize
the code as being !TARGET_SGI though.

-eric

-- 
I will not carve gods


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