On Tue, 3 Jan 2023, Iain Sandoe wrote:
> 1. Modula-2 should not forward the builtins unless the target supports them,
> either by expansion or the relevant lib functions. So that would need
> some
>configury and conditional build code.
Note that such configure tests could only readily
Thanks Joseph,
> On 3 Jan 2023, at 18:15, Joseph Myers wrote:
>
> On Sat, 31 Dec 2022, Iain Sandoe wrote:
>
>> builtins.def unconditionally defines these builtins to be DEF_EXT_LIB_BUILTIN
>> which expands to the libcall, this is currently hard-wired to FALLBACK_P =
>> true.
>>
>> but, AFAIU
On Sat, 31 Dec 2022, Iain Sandoe wrote:
> builtins.def unconditionally defines these builtins to be DEF_EXT_LIB_BUILTIN
> which expands to the libcall, this is currently hard-wired to FALLBACK_P =
> true.
>
> but, AFAIU the builtins.def descriptions:
>
> FALLBACK_P should be false if the libc
Hi Joseph,
> On 30 Dec 2022, at 22:26, Joseph Myers wrote:
>
> On Fri, 30 Dec 2022, Iain Sandoe via Gcc-patches wrote:
>
>> This patch is providing functions used by the modula-2 implementation.
>>
>> At present, I've used a crt rather than adding symbols to libgcc, since
>> it is not clear
On Fri, 30 Dec 2022, Iain Sandoe via Gcc-patches wrote:
> This patch is providing functions used by the modula-2 implementation.
>
> At present, I've used a crt rather than adding symbols to libgcc, since
> it is not clear if the modula-2 might alter the use of scalb to scalbn
> (although that
This patch is providing functions used by the modula-2 implementation.
At present, I've used a crt rather than adding symbols to libgcc, since
it is not clear if the modula-2 might alter the use of scalb to scalbn
(although that will not solve the missing significand* symbols).
I plan to apply
