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
Am 29.07.24 um 11:22 schrieb Jonathan Wakely via Gcc:
> # If a testcase doesn't have special options, use these.
> global DEFAULT_FFLAGS
> if ![info exists DEFAULT_FFLAGS] then {
> set DEFAULT_FFLAGS " -pedantic-errors"
> }
I tried using that, still saw a lot of errors when compiling
C files.
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
>
> $
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
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
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
$ make check-fortran RUNTESTFLAGS="--target_board=unix/-funsigned"
but
