On 27 April 2024 22:02:21 CEST, rep.dot@gmail.com wrote:
>On 27 April 2024 16:11:32 CEST, Jerry D wrote:
>
>>
>>I found these (and several more) patches dated around 2018.
>>
>>https://gcc.gnu.org/git/?p=gcc-old.git;a=commitdiff;h=d38e734485cc84ed0eda7f30b16fb62bdb0cb174
>
>IOPARM_type_char2 s
On 27 April 2024 16:11:32 CEST, Jerry D wrote:
>
>I found these (and several more) patches dated around 2018.
>
>https://gcc.gnu.org/git/?p=gcc-old.git;a=commitdiff;h=d38e734485cc84ed0eda7f30b16fb62bdb0cb174
IOPARM_type_char2 stands out. I do not remember why, but it looks odd that I
had to not
On 4/26/24 2:47 AM, Tobias Burnus wrote:
Hi Bernhard, hello all,
Bernhard Reutner-Fischer wrote:
PS: unfortunately the git branch (
https://gcc.gnu.org/git/?p=gcc.git;a=log;h=refs/heads/aldot/fortran-fe-stringpool
) mentioned in mail (I) lived in the old git, before we switched to
git, and i
On Fri, Apr 26, 2024, 2:47 AM Tobias Burnus wrote:
> Hi Bernhard, hello all,
> Bernhard Reutner-Fischer wrote:
>
> PS: unfortunately the git branch
> (https://gcc.gnu.org/git/?p=gcc.git;a=log;h=refs/heads/aldot/fortran-fe-stringpool
> ) mentioned in mail (I) lived in the old git, before we swit
Hi Bernhard, hello all,
Bernhard Reutner-Fischer wrote:
PS: unfortunately the git branch (
https://gcc.gnu.org/git/?p=gcc.git;a=log;h=refs/heads/aldot/fortran-fe-stringpool
) mentioned in mail (I) lived in the old git, before we switched to
git, and i fear that branch maybe got lost.
Try gcc
Hi Jerry, all!
Just a quick comment for that area.
On Thu, 25 Apr 2024 20:00:24 -0700
Jerry D wrote:
> Hi posted some thoughts on the subject at our mattermost workspace.
>
> This particular PR caught my attention because I have done things like
> this before. I am looking forward to gcc15. I
