Hello world,
I just committed the attached documentatin patch as obvious,
in r15-5344-gbf00f117eb4b5527592029e39a3d79f2048745d8 .
Best regards
Thomas
Document that SELECT CASE works for unsigned.
gcc/fortran/ChangeLog:
* gfortran.texi: Document that SELECT CASE works for UNSI
Hi Thomas,
This has to be the shortest interval between submission and pushing of a
patch that I have experienced!
Pushed to mainline as r15-5347...
Thanks for the review!
Paul
On Sat, 16 Nov 2024 at 15:46, Thomas Koenig wrote:
> Hi Paul,
>
>
> > This is a particularly straightforward, goin
On Sat, Nov 16, 2024 at 02:55:11PM +0100, Thomas Koenig wrote:
>
> Steve found a test case where unsigned constants were not handled
> in a module. Single-line patch committed as obvious and simple,
> r15-5341-g66096151afc6631f8f2a3458b154c5daa822b963 .
>
> Best regards
>
> Thomas
>
Than
Hi Paul,
This is a particularly straightforward, going on 'obvious', patch. The
bug goes back to at least gcc-6.4.1.
OK for mainline and, after a week or two, to 13- and 14-branches?
As you say, this one is straightforward.
OK for trunk and as far back as you care to backport.
Thanks for
Hi All,
This is a particularly straightforward, going on 'obvious', patch. The bug
goes back to at least gcc-6.4.1.
OK for mainline and, after a week or two, to 13- and 14-branches?
Regards
Paul
Change.Logs
Description: Binary data
diff --git a/gcc/fortran/resolve.cc b/gcc/fortran/resolve.cc
Hello world,
Steve found a test case where unsigned constants were not handled
in a module. Single-line patch committed as obvious and simple,
r15-5341-g66096151afc6631f8f2a3458b154c5daa822b963 .
Best regards
Thomas
Handle unsigned constants for module I/O.
gcc/fortran/ChangeLog: