Le 28/01/2023 à 03:47, Jerry D a écrit :
It is not apparent to me that the testsuite/ChangeLog was updated. Maybe
there is a time delay on that?
Yes, it's done daily as part of the "daily bump" commit.
You can see it in the git log:
$ git log -- gcc/testsuite/ChangeLog
commit f457a62e63a86d
Committed:
It is not apparent to me that the testsuite/ChangeLog was updated. Maybe
there is a time delay on that?
Please be patient with me as I figure out how all this works.
ommit f963705752e9d0b79a340788166269af417e344e (HEAD -> master,
origin/master, origin/HEAD)
Author: Jerry DeLisle
On 1/22/23 5:38 AM, Mikael Morin wrote:
Hello,
Le 22/01/2023 à 00:59, Jerry D via Fortran a écrit :
(...)
Proposed ChangeLog entry using git gcc-commit-mklog:
Author: Jerry DeLisle
Date: Sat Jan 21 15:47:19 2023 -0800
Revise the line end tests to pass on certain windows test
environ
Hello,
Le 22/01/2023 à 00:59, Jerry D via Fortran a écrit :
(...)
Proposed ChangeLog entry using git gcc-commit-mklog:
Author: Jerry DeLisle
Date: Sat Jan 21 15:47:19 2023 -0800
Revise the line end tests to pass on certain windows test environments
which inject spurious /r charac
On Sat, Jan 21, 2023, 18:59 Jerry D via Fortran wrote:
>
> Proposed ChangeLog entry using git gcc-commit-mklog:
>
> Author: Jerry DeLisle
> Date: Sat Jan 21 15:47:19 2023 -0800
>
> Revise the line end tests to pass on certain windows test environments
> which inject spurious /r chara
On 1/20/23 6:13 PM, Jerry DeLisle via Fortran wrote:
Hi all,
The attached patch modifies the following tests to check for line
endings. Some test environments inject superfluous /r characters at
ends of lines. The expression matching in dg-output tests are changed from:
(\n|\r\n|\r)
to
(\r*\
