[Bug libfortran/93727] Fortran 2018: EX edit descriptor
jvdelisle at gcc dot gnu.org
gcc-bugzilla@gcc.gnu.org
Tue May 26 21:44:26 GMT 2026
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93727
--- Comment #40 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
(In reply to Harald Anlauf from comment #39)
--- snip ---
> > I have added a new testcase called EXrounding.F90 to do this. I have style
> > checks done as well. As soon as I go through a clean pull and fresh
> > regression tests, I will push. Thanks Harald.
>
> Please do not forget to inform the list!
>
> BTW: I see testsuite failures on Power. Not sure if related, but I see
> also warnings compiling libgfortran/io/write.c:
>
> In file included from ../../../gcc-trunk/libgfortran/io/write.c:53:
> ../../../gcc-trunk/libgfortran/io/write_float.def: In Funktion
> »get_float_hex_string«:
> ../../../gcc-trunk/libgfortran/io/write_float.def:177:57: warning: Format
> »%llX« erwartet Argumenttyp »long long unsigned int«, aber Argument 5 hat
> Typ »long unsigned int« [-Wformat=]
> 177 | result = snprintf (buffer, 25, "-0X%X.%13.13llXP%+d",
> int_part,
> | ~~~~~~~~^
> | |
> | long long
> unsigned int
> | %13.13lX
> 178 | (GFC_UINTEGER_8) frac_part, expon);
> | ~~~~~~~~~~~~~~~~~~~~~~~~~~
> | |
> | long unsigned int
>
> I think the warnings are correct, and wonder whether one should use/pass
> (long long unsigned) instead of (GFC_UINTEGER_8).
That warning bothers me too. I am just finishing regression tests here. I will
submit to the lists before I commit. See if the auto testers catch anything.
Let me know if you see specific testsuite failres on power.
More information about the Gcc-bugs
mailing list