On Wed, 4 Sep 2019 at 01:22, Jeff Law wrote:
>
> On 8/28/19 8:55 PM, Prathamesh Kulkarni wrote:
> > Hi,
> > This is a rebased patch on trunk for PR78736. The last time, it got
> > stuck, because of warning issues with libgfortran, for which I filed
> > PR91593. T
On 8/28/19 8:55 PM, Prathamesh Kulkarni wrote:
> Hi,
> This is a rebased patch on trunk for PR78736. The last time, it got
> stuck, because of warning issues with libgfortran, for which I filed
> PR91593. The patch relegates the warning to Wextra instead, which only
> triggers (non-
Hi,
This is a rebased patch on trunk for PR78736. The last time, it got
stuck, because of warning issues with libgfortran, for which I filed
PR91593. The patch relegates the warning to Wextra instead, which only
triggers (non-fatal) warnings in libgfortran/io/transfer.c, and
survives bootstrap
On 06/29/2017 05:01 PM, Joseph Myers wrote:
> On Thu, 29 Jun 2017, Jeff Law wrote:
>
>> On 05/23/2017 07:54 AM, Prathamesh Kulkarni wrote:
>>> Hi,
>>> I would like to ping this patch for review:
>>> https://gcc.gnu.org/ml/gcc-patches/2017-05/msg00775.html
>> So was there any kind of resolution on
On Thu, 29 Jun 2017, Jeff Law wrote:
> On 05/23/2017 07:54 AM, Prathamesh Kulkarni wrote:
> > Hi,
> > I would like to ping this patch for review:
> > https://gcc.gnu.org/ml/gcc-patches/2017-05/msg00775.html
> So was there any kind of resolution on the case in libcomp where we had
> an assignment
On 05/23/2017 07:54 AM, Prathamesh Kulkarni wrote:
> Hi,
> I would like to ping this patch for review:
> https://gcc.gnu.org/ml/gcc-patches/2017-05/msg00775.html
So was there any kind of resolution on the case in libcomp where we had
an assignment between two essentially equivalent, but distinct
Hi,
I would like to ping this patch for review:
https://gcc.gnu.org/ml/gcc-patches/2017-05/msg00775.html
Thanks,
Prathamesh
Hi,
I would like to ping this patch for review:
https://gcc.gnu.org/ml/gcc-patches/2017-05/msg00775.html
Thanks,
Prathamesh
