Am 29.07.24 um 22:14 schrieb Thomas Schwinge:
By the way: I did see your recent announcement; wow -- Fortran finally
getting an UNSIGNED type! 🙂
Yep, at lest J3 accepted a propoasl.
I would like to be able to run all
existing Fortran tests also with -funsigned, to make sure the option
does
Hi Thomas!
On 2024-07-29T10:18:49+0200, Thomas Koenig via Gcc wrote:
> for the fortran-unsigned branch
By the way: I did see your recent announcement; wow -- Fortran finally
getting an UNSIGNED type! :-)
> I would like to be able to run all
> existing Fortran tests also with -funsigned, to mak
Hi Andrew,
Any other possibilites?
Yes you could add it into the list of Torture options that
gfortran-dg-runtest uses.
Something like:
```
diff --git a/gcc/testsuite/lib/gfortran-dg.exp
b/gcc/testsuite/lib/gfortran-dg.exp
index fcba95dc396..0589d507382 100644
--- a/gcc/testsuite/lib/gfortran-d
On Mon, Jul 29, 2024 at 1:20 AM Thomas Koenig wrote:
>
> Hi,
>
> for the fortran-unsigned branch, I would like to be able to run all
> existing Fortran tests also with -funsigned, to make sure the option
> does not break anything on existing code.
>
> Question is: How?
>
> I came as far as
>
> $ m
On Mon, 29 Jul 2024 at 10:20, Jonathan Wakely wrote:
>
> On Mon, 29 Jul 2024 at 09:20, Thomas Koenig via Gcc wrote:
> >
> > Hi,
> >
> > for the fortran-unsigned branch, I would like to be able to run all
> > existing Fortran tests also with -funsigned, to make sure the option
> > does not break a
On Mon, 29 Jul 2024 at 09:20, Thomas Koenig via Gcc wrote:
>
> Hi,
>
> for the fortran-unsigned branch, I would like to be able to run all
> existing Fortran tests also with -funsigned, to make sure the option
> does not break anything on existing code.
>
> Question is: How?
>
> I came as far as
>
