public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Eric Christopher <echristo@apple.com>
To: Thiemo Seufer <ths@networkno.de>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] Better checking of ISA/ASE/ABI options for MIPS gas
Date: Tue, 23 May 2006 05:01:00 -0000	[thread overview]
Message-ID: <A9F8D906-B293-44CF-A220-E4E1798F60F0@apple.com> (raw)
In-Reply-To: <20060522234641.GA9061@networkno.de>

>>
>> No. No more reading the minds of programmers. :)
>
> Well, for GP registers we do even as_bad().

Yup.

>> And why change the table to include default extensions for the cpu?
>
> To handle them the same way as the ISA. This is for ASEs which are
> always implemented in that particular CPU.

You'll need to look through the code and make sure we aren't  
depending on
the value not being zero somewhere then. To be honest I'd just prefer  
another
field for "default ASEs".

>>>   /* End of GCC-shared inference code.  */
>>
>> You need to make sure that this shared code is the same logic in both
>> places - preferably before committing this.
>
> Yes. Do you think the logic is ok (modulo the FP ABI warning)?

I do. :)

>>> +#if 0 /* XXX FIXME */
>>> +  /* 32 bit code with 64 bit FP registers.  */
>>> +  if (!file_mips_fp32 && ABI_NEEDS_32BIT_REGS (mips_abi))
>>> +    elf_elfheader (stdoutput)->e_flags |= ???;
>>> +#endif
>>> }
>>>
>>
>> ???
>
> Same like for MIPS3D, we should tell the linker this object is  
> (possibly)
> incompatible to other O32 objects with 32bit FP regs.

More comments then :)

-eric

  reply	other threads:[~2006-05-22 23:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-23  0:08 Thiemo Seufer
2006-05-23  4:06 ` Eric Christopher
2006-05-23  4:40   ` Thiemo Seufer
2006-05-23  5:01     ` Eric Christopher [this message]
2006-05-23  5:27       ` Thiemo Seufer
2006-05-23  5:51         ` Eric Christopher
2006-05-23 12:10 ` Richard Sandiford
2006-05-23 13:34   ` Thiemo Seufer
2006-05-23 14:14     ` Richard Sandiford
2006-05-23 15:39       ` Thiemo Seufer
2006-05-23 17:47 ` Thiemo Seufer
2006-05-23 21:01   ` Richard Sandiford
2006-05-23 23:37     ` Thiemo Seufer
2006-05-24  1:46       ` Richard Sandiford

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=A9F8D906-B293-44CF-A220-E4E1798F60F0@apple.com \
    --to=echristo@apple.com \
    --cc=binutils@sourceware.org \
    --cc=ths@networkno.de \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).