[14/25] Specs cleanup: MIPS -call_shared -non_shared

In addition to the specs mentioned in patch 13, various MIPS targets
have specs passing -call_shared and -non_shared to the linker.  While
these options do exist with the GNU linker, there is nothing
MIPS-specific about them and there should be nothing MIPS-specific
about such options being accepted by the driver; the appropriate
dependence is on the target operating system.  Thus, this patch
removes them also from specs for non-IRIX targets.  OK to commit?

2011-01-13  Joseph Myers  <joseph@codesourcery.com>

	* config/mips/linux64.h (LINK_SPEC): Remove %{non_shared}
	%{call_shared}.
	* config/mips/mips.h (LINK_SPEC): Remove %{non_shared}.
	* config/mips/netbsd.h (LINK_SPEC): Remove %{call_shared}.
	* config/mips/openbsd.h (LINK_SPEC): Remove %{non_shared}
	%{call_shared} and conditionals on these options not being passed.
	* config/mips/sde.h (LINK_SPEC): Remove %{non_shared}
	%{call_shared}.

"Joseph S. Myers" <joseph@codesourcery.com> writes:
> In addition to the specs mentioned in patch 13, various MIPS targets
> have specs passing -call_shared and -non_shared to the linker.  While
> these options do exist with the GNU linker, there is nothing
> MIPS-specific about them and there should be nothing MIPS-specific
> about such options being accepted by the driver; the appropriate
> dependence is on the target operating system.  Thus, this patch
> removes them also from specs for non-IRIX targets.  OK to commit?

I'm not sure this is a good idea.  I'd agree with your logic if we
were starting from scratch, but I don't see the need to change from
historical precendent now.

Richard

On Fri, 14 Jan 2011, Richard Sandiford wrote:

> "Joseph S. Myers" <joseph@codesourcery.com> writes:
> > In addition to the specs mentioned in patch 13, various MIPS targets
> > have specs passing -call_shared and -non_shared to the linker.  While
> > these options do exist with the GNU linker, there is nothing
> > MIPS-specific about them and there should be nothing MIPS-specific
> > about such options being accepted by the driver; the appropriate
> > dependence is on the target operating system.  Thus, this patch
> > removes them also from specs for non-IRIX targets.  OK to commit?
> 
> I'm not sure this is a good idea.  I'd agree with your logic if we
> were starting from scratch, but I don't see the need to change from
> historical precendent now.

The immediate motivation is getting all options into .opt files so that 
the driver can (in 4.7) start rejecting options not known in a .opt file 
rather than accepting them if matched by some spec.

While of course these options can be added to a .opt file or files (it's 
fairly harmless for a .opt file to list some options that are not in fact 
accepted by specs for all targets using that .opt file), there seems to be 
very little logic about which are accepted where.  mips/linux64.h accepts 
both, mips/linux.h accepts neither, mips/mips.h accepts only -non_shared, 
mips/netbsd.h accepts only -call_shared - so there is no consistency of 
design even for MIPS targets here.  And since a strength of GCC is 
consistency between different targets, making things consistent by 
removing them from specs where they are accepted for MIPS but not other 
targets with same OS seems natural.

(In general I think it would be a good idea for much more spec content to 
be shared between targets.  The main content of LINK_SPEC for 
GNU-userspace targets, for example, could go in a $(gnu_user_link_spec) 
(or even $(gnu_ld_elf_link_spec)) whose contents are exactly those of the 
i386/linux.h LINK_SPEC (after my patch 05); each target architecture would 
define link_emulation and dynamic_linker specs to go along with this, and 
LINK_SPEC would be defined in <arch>/linux.h to contain 
$(gnu_user_link_spec) plus such other pieces as are genuinely 
architecture-specific.)

"Joseph S. Myers" <joseph@codesourcery.com> writes:
> On Fri, 14 Jan 2011, Richard Sandiford wrote:
>> "Joseph S. Myers" <joseph@codesourcery.com> writes:
>> > In addition to the specs mentioned in patch 13, various MIPS targets
>> > have specs passing -call_shared and -non_shared to the linker.  While
>> > these options do exist with the GNU linker, there is nothing
>> > MIPS-specific about them and there should be nothing MIPS-specific
>> > about such options being accepted by the driver; the appropriate
>> > dependence is on the target operating system.  Thus, this patch
>> > removes them also from specs for non-IRIX targets.  OK to commit?
>> 
>> I'm not sure this is a good idea.  I'd agree with your logic if we
>> were starting from scratch, but I don't see the need to change from
>> historical precendent now.
>
> The immediate motivation is getting all options into .opt files so that 
> the driver can (in 4.7) start rejecting options not known in a .opt file 
> rather than accepting them if matched by some spec.
>
> While of course these options can be added to a .opt file or files (it's 
> fairly harmless for a .opt file to list some options that are not in fact 
> accepted by specs for all targets using that .opt file), there seems to be 
> very little logic about which are accepted where.  mips/linux64.h accepts 
> both, mips/linux.h accepts neither, mips/mips.h accepts only -non_shared, 
> mips/netbsd.h accepts only -call_shared - so there is no consistency of 
> design even for MIPS targets here.

OK, that's a convincing argument.  I hadn't realised that linux.h and
linux64.h did different things here.  Since linux.h doesn't have them,
I agree there's very little to worry about.

I'll echo Eric's OK.

Richard