Richard Sandiford wrote:
Zack Weinberg <[EMAIL PROTECTED]> writes:
Richard Sandiford <[EMAIL PROTECTED]> writes:
The only reliable way to get what you want is to either (a) add -G0
multilibs or (b) change the default -G setting. Perhaps a configure
option would be useful here. Maybe something lik
Zack Weinberg <[EMAIL PROTECTED]> writes:
> Richard Sandiford <[EMAIL PROTECTED]> writes:
>> The only reliable way to get what you want is to either (a) add -G0
>> multilibs or (b) change the default -G setting. Perhaps a configure
>> option would be useful here. Maybe something like --with-sdata
Richard Sandiford <[EMAIL PROTECTED]> writes:
> The only reliable way to get what you want is to either (a) add -G0
> multilibs or (b) change the default -G setting. Perhaps a configure
> option would be useful here. Maybe something like --with-sdata-limit,
> to go alongside options like --with-
Jonathan Larmour <[EMAIL PROTECTED]> writes:
> On MIPS, libgcc is built with -G 0, which is used to ensure the contents
> don't assume they will be placed in the small data/bss section. Setting
> -G 0 is used to allow for the possibility of large applications, or
> those where even small data may b
On MIPS, libgcc is built with -G 0, which is used to ensure the contents
don't assume they will be placed in the small data/bss section. Setting -G
0 is used to allow for the possibility of large applications, or those
where even small data may be located more than 64k away from the gp pointer.
