public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Moore, Catherine" <Catherine_Moore@mentor.com>
To: Matthew Fortune <Matthew.Fortune@imgtec.com>
Cc: "'gcc-patches@gcc.gnu.org' (gcc-patches@gcc.gnu.org)"
	<gcc-patches@gcc.gnu.org>
Subject: RE: [MIPS] Re-enable ABI->ISA inference
Date: Wed, 14 Jan 2015 00:44:00 -0000	[thread overview]
Message-ID: <FD3DCEAC5B03E9408544A1E416F112420189146139@NA-MBX-04.mgc.mentorg.com> (raw)
In-Reply-To: <6D39441BF12EF246A7ABCE6654B0235320F95F07@LEMAIL01.le.imgtec.org>



> -----Original Message-----
> From: Matthew Fortune [mailto:Matthew.Fortune@imgtec.com]
> Sent: Monday, January 05, 2015 6:09 PM
> To: Moore, Catherine
> Cc: 'gcc-patches@gcc.gnu.org' (gcc-patches@gcc.gnu.org)
> Subject: [MIPS] Re-enable ABI->ISA inference
> 
> The R6 patch introduced MIPS_ISA_LEVEL_SPEC into DRIVER_SELF_SPECS for
> all configurations. One part of MIPS_ISA_LEVEL_SPEC is however
> incompatible with those configurations which infer an ISA from an ABI
> without specifically setting the default ISAs using --with-arch-[32|64].
> 
> I.e. a generic mips-linux (--enable-targets=all) and mips64-linux would fail to
> build the n32/n64 multilibs as -mips1 would be introduced by
> DRIVER_SELF_SPECS.
> 
> I have therefore split MIPS_ISA_LEVEL_SPEC into two. One part is suitable
> for all confgurations and one part is only suitable for configurations that infer
> an ABI from an ISA (these tend to be cross-compiler vendor configurations)
> 
> I have built and checked the driver generated options for all relevant
> configurations and everything appears to work.
> 
> Let me know if you can see any problems with this?
> 
> Thanks,
> Matthew
> 
> gcc/
> 
>      * config/mips/mips.h (MIPS_ISA_LEVEL_SPEC): Only infer an ISA
>      level from an ARCH; do not inject the default.
>      (MIPS_DEFAULT_ISA_LEVEL_SPEC): New macro split out from
>      MIPS_ISA_LEVEL_SPEC.
>      (MIPS_ISA_NAN2008_SPEC): Update comment.
>      (BASE_DRIVER_SELF_SPECS): Likewise.
>      * config/mips/elfoabi.h (DRIVER_SELF_SPECS): Add
>      MIPS_DEFAULT_ISA_LEVEL_SPEC.
>      * config/mips/mti-elf.h (DRIVER_SELF_SPECS): Likewise.
>      * config/mips/mti-linux.h (DRIVER_SELF_SPECS): Likewise.
>      * config/mips/sde.h (DRIVER_SELF_SPECS): Likewise.
> ---

This looks OK.

  reply	other threads:[~2015-01-13 23:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05 23:09 Matthew Fortune
2015-01-14  0:44 ` Moore, Catherine [this message]
2015-01-14  9:10   ` Matthew Fortune

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=FD3DCEAC5B03E9408544A1E416F112420189146139@NA-MBX-04.mgc.mentorg.com \
    --to=catherine_moore@mentor.com \
    --cc=Matthew.Fortune@imgtec.com \
    --cc=gcc-patches@gcc.gnu.org \
    /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).