Hi Steve, hi all,
the patch for pr98301 has been backported to gcc-11 as
002745ca3668fc5e87c22acc81caaeaaadf9c47a
Regards,
Andre
On Sat, 5 Jun 2021 09:27:16 -0700
Steve Kargl wrote:
> On Sat, Jun 05, 2021 at 04:04:51PM +0200, Andre Vehreschild wrote:
> >
> > I was asked to backport the
On Sat, Jun 05, 2021 at 04:04:51PM +0200, Andre Vehreschild wrote:
>
> I was asked to backport the patch for pr98301 to gcc-11. The patches have
> been in mainline for two weeks without any defect reports I could fined. The
> patch for mainline applied with a bit of shift cleanly.
>
> Regstested
Hi all,
I was asked to backport the patch for pr98301 to gcc-11. The patches have
been in mainline for two weeks without any defect reports I could fined. The
patch for mainline applied with a bit of shift cleanly.
Regstested fine on x86_64/f33. Ok for backport gcc-11?
Regards,
Andre
--
On 5/23/21 1:59 PM, Andre Vehreschild wrote:
Hi Martin,
thanks for pointing that out. I haven't committed for quite some time now and
could not find on the webpage how this works nowadays. I was thinking that the
special gcc-git-command should have added the Changelog entries automagically
and i
Hi Martin,
thanks for pointing that out. I haven't committed for quite some time now and
could not find on the webpage how this works nowadays. I was thinking that the
special gcc-git-command should have added the Changelog entries automagically
and immediately. That they are added by a daily bump
On 5/22/21 1:39 PM, Andre Vehreschild via Gcc-patches wrote:
Hi Steve and Jerry,
thanks for the ok'ing.
Committed as https://gcc.gnu.org/g:26ca6dbda23bc6dfab96ce07afa70ebacedfaf9c
and https://gcc.gnu.org/g:c4771b3438a8cd9afcef1762957b763f8df3fa6e (for the
missing changelog entries).
Hello.
A
Hi Steve and Jerry,
thanks for the ok'ing.
Committed as https://gcc.gnu.org/g:26ca6dbda23bc6dfab96ce07afa70ebacedfaf9c
and https://gcc.gnu.org/g:c4771b3438a8cd9afcef1762957b763f8df3fa6e (for the
missing changelog entries).
- Andre
On Fri, 21 May 2021 19:38:00 -0700
Jerry D wrote:
> yes, pleas
yes, please commit
On 5/21/21 8:08 AM, Steve Kargl via Fortran wrote:
On Fri, May 21, 2021 at 10:09:02AM +0200, Andre Vehreschild wrote:
Ping, ping!
Please find attached a rebased version of the patch for the RANDOM_INIT issue
with coarray Fortran. Nothing changed to the previous version, just
On Fri, May 21, 2021 at 10:09:02AM +0200, Andre Vehreschild wrote:
> Ping, ping!
>
> Please find attached a rebased version of the patch for the RANDOM_INIT issue
> with coarray Fortran. Nothing changed to the previous version, just rebased to
> current master.
>
> Regtested fine on x86_64-linux/
Ping, ping!
Please find attached a rebased version of the patch for the RANDOM_INIT issue
with coarray Fortran. Nothing changed to the previous version, just rebased to
current master.
Regtested fine on x86_64-linux/f33. Ok for trunk?
- Andre
On Mon, 3 May 2021 08:20:36 -0700
Steve Kargl wrote
On Mon, May 03, 2021 at 11:21:10AM +0200, Andre Vehreschild wrote:
> Ping!
>
> Ok for trunk?
>
> I have looked at other patches, but none was patching any location I have
> worked on previously. Therefore I can't return the favor of reviewing any
> currently open patches and have to ask for volun
Ping!
Ok for trunk?
I have looked at other patches, but none was patching any location I have
worked on previously. Therefore I can't return the favor of reviewing any
currently open patches and have to ask for volunteers here.
- Andre
On Mon, 26 Apr 2021 12:36:36 +0200
Andre Vehreschild via Fo
Hi Steve, hi all,
I agree. The cas-things have been removed (I will put the patch for them into
the pr98301 ticket, so safe them), streamlining the patch a bit more.
Bootstraped and regtested ok on x86_64-linux/f33. Ok for trunk?
Regards,
Andre
Steve Kargl
PR fortran/98301 - random_
On Sat, Apr 24, 2021 at 12:49:45PM +0200, Andre Vehreschild wrote:
> Hi Steve, hi all,
>
> thank you for pointing that out, Steve. When I started the work, I told
> myself, that I have to remember to add your patch to the submit. Well, that
> did
> not last for more than eight hours and I had for
Ok, I changed it in the log-file already.
- Andre
On Sat, 24 Apr 2021 08:44:24 -0700
Steve Kargl wrote:
> On Sat, Apr 24, 2021 at 12:49:45PM +0200, Andre Vehreschild wrote:
> >
> > @Steve: Is this your correct mail address for the changelog or do you
> > prefer a different one?
> >
>
> I s
On Sat, Apr 24, 2021 at 12:49:45PM +0200, Andre Vehreschild wrote:
>
> @Steve: Is this your correct mail address for the changelog or do you prefer a
> different one?
>
I still have my ka...@gcc.gnu.org email address. Please use that one.
I'll look over the combined patch later today.
--
Stev
Hi Steve, hi all,
thank you for pointing that out, Steve. When I started the work, I told
myself, that I have to remember to add your patch to the submit. Well, that did
not last for more than eight hours and I had forgotten.
So here is now the combination of Steve's and my patch (attached).
Boo
Andre,
Thanks for taking care of OpenCoarray portion of RANDOM_INIT.
My last non-coarray aware patch is attached to the PR in bugzilla.
Since the change over to git, I no longer commit to the source tree.
I suggest combining your patch with my patch if you intend to
commit; otherwise, attach your
Hi folks,
please find attached the library part for supporting RANDOM_INIT for
coarray=lib enabled fortran translations. There is also a patch for the
Opencoarray library to add RANDOM_INIT there.
I am not sure, whether I have modified the gfortran.map file in the libgfortran
directory correctly,
On Sat, Apr 03, 2021 at 08:30:31PM -0700, Damian Rouson wrote:
> Hi Steve,
>
> I hope the gfortran developers won't commit a patch that replaces
> existing behavior with a stub that simply emits an error message.
The current behavior is incorrect with respect to the Fortran standard
if one runs a
Hi Steve,
I hope the gfortran developers won't commit a patch that replaces
existing behavior with a stub that simply emits an error message. It
has been a while since I looked at the previous emails regarding
problems with the current behavior so I'm not expressing an opinion
about the current b
21 matches
Mail list logo
