[patch] Fix PR fortran/96983

2021-03-08 Thread Eric Botcazou
Hi, AFAICS the code in build_round_expr implicitly assumes that __float128 exists, which is *not* the common case among 64-bit architectures since "long double" is generally already 128-bit for them. Tested on x86-64/Linux and SPARC64/Linux, OK for the mainline? 2021-03-08 Eri

Re: [patch] Fix PR fortran/96983

2021-03-10 Thread Eric Botcazou
); > fn = gfc_builtin_decl_for_float_kind (BUILT_IN_ROUND, kind); > } > else Yes, it works fine on x86-64/Linux and SPARC64/Linux, applied, thanks. -- Eric Botcazou

Re: [PATCH][v2] Adjust volatile handling of the operand scanner

2021-08-10 Thread Eric Botcazou
What do we do for other similar flags, e.g. TREE_READONLY? -- Eric Botcazou

Re: [PATCH][v2] Adjust volatile handling of the operand scanner

2021-08-11 Thread Eric Botcazou
when the FIELD_DECL has > TREE_THIS_VOLATILE set. This would be weird semantics in my opinion. > I guess I'll do one more experiment and add verification that > TREE_THIS_VOLATILE on COMPONENT_REFs and FIELD_DECLs is consistent > and see where that trips. Sounds good to me. -- Eric Botcazou

Re: [PATCH][v2] Adjust volatile handling of the operand scanner

2021-08-11 Thread Eric Botcazou
> So I'm leaning towards leaving build3 alone and fixing up frontends > as issues pop up. FWIW fine with me. -- Eric Botcazou

Re: Adding a new thread model to GCC

2023-01-09 Thread Eric Botcazou via Fortran
> fixed now. > bootstrapped successfully! Thanks for fixing it. Another way out is to hide the Win32 API by defining __GTHREAD_HIDE_WIN32API like libstdc++ does in its header files. -- Eric Botcazou