> From: Richard Sandiford [mailto:rdsandif...@googlemail.com]
>
> Yes. The configurations that support -mno-float have separate -mno-float
> multilibs. In a sense, the point of -mno-float instead of -msoft-float is
> to select these cut-down libraries.
IIRC, glibc loads some code on demand to a
"Thomas Preud'homme" writes:
>> From: Richard Sandiford [mailto:rdsandif...@googlemail.com]
>>
>> "Thomas Preud'homme" writes:
>>
>> -mno-float causes gcc to define the macro __mips_no_float, which the
>> implementation can use when deciding whether to bother handling %f, etc.
>> I'm afraid the
> From: Richard Sandiford [mailto:rdsandif...@googlemail.com]
>
> "Thomas Preud'homme" writes:
>
> -mno-float causes gcc to define the macro __mips_no_float, which the
> implementation can use when deciding whether to bother handling %f, etc.
> I'm afraid there's nothing more sophisticated to it
"Thomas Preud'homme" writes:
>> From: Richard Sandiford [mailto:rdsandif...@googlemail.com]
>>
>> -mno-float as it stands today is really just -msoft-float with some
>> floating-point support removed from the library to save space.
>> One of the important examples is that the floating-point print
On Tue, 18 Mar 2014, Thomas Preud'homme wrote:
> > From: gcc-ow...@gcc.gnu.org [mailto:gcc-ow...@gcc.gnu.org] On Behalf Of
> > Joseph S. Myers
> >
> > The functions affected use floating-point in their public interfaces - for
> > example, __muldc3. Note that libcalls have a different hook
> > (T
> From: Richard Sandiford [mailto:rdsandif...@googlemail.com]
>
> -mno-float as it stands today is really just -msoft-float with some
> floating-point support removed from the library to save space.
> One of the important examples is that the floating-point printf
> and scanf formats are not suppo
> From: gcc-ow...@gcc.gnu.org [mailto:gcc-ow...@gcc.gnu.org] On Behalf Of
> Joseph S. Myers
>
> The functions affected use floating-point in their public interfaces - for
> example, __muldc3. Note that libcalls have a different hook
> (TARGET_LIBCALL_VALUE, ending up using arm_libcall_uses_aapcs_
On Wed, 5 Mar 2014, Thomas Preud'homme wrote:
> > Some libgcc functions on ARM have ABIs that depend on which AAPCS
> > variant is in use - that is, libcalls, not just explicitly defined or
> > called functions, can affect the ABI compatibility. But the RTABI
> > functions don't - if you allow
> From: Richard Sandiford [mailto:rdsandif...@googlemail.com]
> Yeah, that'd be great. The checking that MIPS's -mno-float should do
> (but doesn't do) would be a superset of what you need, since the MIPS
> case would include internal uses of floats. But it would definitely
> make sense to share
[Since I can now send emails without disclaimers, I registered to the mailing
list with my work email. Thus no need to CC me anymore.]
My apologize for the line length, the MUA says it all I think. It seems to
ignore my word wrap setting
> From: Joseph Myers [mailto:jos...@codesourcery.com]
> S
> From: Thomas Preud'homme
> [Since I can now send emails without disclaimers, I registered to the mailing
> list with my work email. Thus no need to CC me anymore.]
Failed in the previous 2 emails. Sorry about that.
Thomas Preudhomme writes:
>> I think the ability to detect the case of generating ABI agnostic
>> code would be useful for other architectures too.
>
> I do not know the other architecture to know if that is the case but
> according to what you said for MIPS it seems to be the case. Right now I
On Wed, 5 Mar 2014, Thomas Preudhomme wrote:
> Right. It's actually quite simple. As soon as you meet a function which passes
> or returns a float then you can mark the whole module as not agnostic and fall
> back to the usual behavior. If you arrive at the end of a compiling unit
> without encout
Le 2014-03-04 19:14, Matthew Fortune a écrit :
Hi Thomas,
Hi Matthew,
Do you particularly need a switch for this? You could view this as
simply relaxing the ABI requirements of a module, a switch would only
serve to enforce the need for a compatible ABI and error if not. If
you build somethi
Hi Thomas,
Do you particularly need a switch for this? You could view this as simply
relaxing the ABI requirements of a module, a switch would only serve to enforce
the need for a compatible ABI and error if not. If you build something for a
soft-float ABI and never actually trigger any of the
15 matches
Mail list logo
