Re: *PING* [PATCH 0/7] fortran: Inline MINLOC/MAXLOC with DIM [PR90608]

2024-11-19 Thread Mikael Morin
Le 18/11/2024 à 20:18, Steve Kargl a écrit : Mikael, I've read through each of the patch and nothing jumped out as an issue. I think you can go ahead and commit them. I'll leave it up to you whether to commit a patch and wait a short time before committing the next in the series. The short t

Re: *PING* [PATCH 0/7] fortran: Inline MINLOC/MAXLOC with DIM [PR90608]

2024-11-18 Thread Steve Kargl
On Fri, Nov 01, 2024 at 01:01:39PM +0100, Mikael Morin wrote: > Le 30/10/2024 à 23:00, Harald Anlauf a écrit : > > > > given that Jakub changed lots of whitespace in r15-4624-g50332a4fdd3243, > > you may want to rebase your patches onto HEAD of trunk. > > > > May I also suggest to attach the patc

Re: *PING* [PATCH 0/7] fortran: Inline MINLOC/MAXLOC with DIM [PR90608]

2024-11-01 Thread Mikael Morin
Le 30/10/2024 à 23:00, Harald Anlauf a écrit : given that Jakub changed lots of whitespace in r15-4624-g50332a4fdd3243, you may want to rebase your patches onto HEAD of trunk. May I also suggest to attach the patches instead of mailing them inline? Hello, I checked with today's master, didn'

Re: *PING* [PATCH 0/7] fortran: Inline MINLOC/MAXLOC with DIM [PR90608]

2024-10-30 Thread Harald Anlauf
Hi Mikael, Am 30.10.24 um 11:23 schrieb Mikael Morin: *PING* The first series of patches was pushed, the second (and last) one [1][2] is awaiting review. [1] https://gcc.gnu.org/pipermail/gcc-patches/2024-October/665360.html [2] https://gcc.gnu.org/pipermail/fortran/2024-October/061180.html

*PING* [PATCH 0/7] fortran: Inline MINLOC/MAXLOC with DIM [PR90608]

2024-10-30 Thread Mikael Morin
*PING* The first series of patches was pushed, the second (and last) one [1][2] is awaiting review. [1] https://gcc.gnu.org/pipermail/gcc-patches/2024-October/665360.html [2] https://gcc.gnu.org/pipermail/fortran/2024-October/061180.html