On 11/13/2025 7:52 AM, Andrew Pinski wrote:
On Wed, Nov 12, 2025 at 11:50 PM Andrew Pinski
<[email protected]> wrote:
On Wed, Nov 12, 2025 at 11:30 PM Evgeny Karpov <[email protected]> wrote:
Saurabh Jha wrote:
In v3, removed libgfortran changes in response to this comment:
https://forge.sourceware.org/gcc/gcc-TEST/pulls/118#issuecomment-3894
It leads to the error below without changes to libgfortran/configure*
and works fine after applying them.
gcc/libgfortran/kinds-override.h:29:3: error: #error "Where has _Float128 gone?"
That would mean TFmode is supported but _Float128 is not; that is not
a supported configuration. So you need to debug why _Float128 is not
being enabled in the C front-end or just disable TFmode for scalar
mode too.
Don't hack libgfortran for this unsupported configure.
A little hint on this is targetm.floatn_mode should return TFmode for
128. if you want to support _Float128.
I am planning to do it as part of another series and focusing this patch
series to only C.
Thanks,
Saurabh
Thanks,
Andrew
Thanks,
Andrew
Validated by
https://github.com/eukarpov/gnu-toolchain-windows-arm64/actions/runs/19315607232/job/55246075637
https://github.com/eukarpov/gnu-toolchain-windows-arm64/actions/runs/19315607232
Regards,
Evgeny
