Re: [Patch, Fortran] PR 69495: unused-label warning does not tell which flag triggered it

>> The patch is OK for trunk. > > thanks a lot. Will commit soon. Committed as r241870. Thanks again. Cheers, Janus >> On 5 November 2016 at 10:15, Janus Weil wrote: >>> Hi all, >>> >>> here is a patch that I had submitted already in February (see >>>

Re: [Patch, Fortran] PR 69495: unused-label warning does not tell which flag triggered it

Hi Paul, > The patch is OK for trunk. thanks a lot. Will commit soon. > PS While you are with us, are you intending to deal with the 14 PRs > for which you are the assignee or will you unassign yourself? Good point. I will look through them and see what I can do. In fact I might have a bit of

Re: [Patch, Fortran] PR 69495: unused-label warning does not tell which flag triggered it

Hi Janus, Welcome back! The patch is OK for trunk. Best regards Paul PS While you are with us, are you intending to deal with the 14 PRs for which you are the assignee or will you unassign yourself? On 5 November 2016 at 10:15, Janus Weil wrote: > Hi all, > > here is a

[Patch, Fortran] PR 69495: unused-label warning does not tell which flag triggered it

Hi all, here is a patch that I had submitted already in February (see https://gcc.gnu.org/ml/fortran/2016-02/msg00011.html). Unfortunately it was never approved and I got distracted with other things and forgot about it. It's a diagnostics patch, which makes sure that the responsible flag is

Re: [Patch, Fortran] PR 69495: unused-label warning does not tell which flag triggered it

double-ping ... 2016-02-12 0:29 GMT+01:00 Janus Weil : > ping! > > 2016-02-05 19:19 GMT+01:00 Janus Weil : >> Hi all, >> >> I have slightly updated the patch now to avoid string-breaking issues >> (even if it may not be a problem at all, as mentioned by

Re: [Patch, Fortran] PR 69495: unused-label warning does not tell which flag triggered it

ping! 2016-02-05 19:19 GMT+01:00 Janus Weil : > Hi all, > > I have slightly updated the patch now to avoid string-breaking issues > (even if it may not be a problem at all, as mentioned by Jospeh). Also > I removed the questionable part in intrinsic.c that I was not sure >

Re: [Patch, Fortran] PR 69495: unused-label warning does not tell which flag triggered it

Hi all, I have slightly updated the patch now to avoid string-breaking issues (even if it may not be a problem at all, as mentioned by Jospeh). Also I removed the questionable part in intrinsic.c that I was not sure about. This version of the patch should not be too far from obvious now. Ok for

Re: [Patch, Fortran] PR 69495: unused-label warning does not tell which flag triggered it

Am 02.02.2016 um 21:26 schrieb Janus Weil: Hi all, here is a diagnostics patch, which makes sure that the responsible flag is printed in several warning messages (for which this was still missing). The only case that I'm not completely sure about is the hunk in intrinsic.c. In particular I

Re: [Patch, Fortran] PR 69495: unused-label warning does not tell which flag triggered it

Am 03.02.2016 um 19:18 schrieb Janus Weil: Hi, 2016-02-03 10:21 GMT+01:00 Manfred Schwarb : here is a diagnostics patch, which makes sure that the responsible flag is printed in several warning messages (for which this was still missing). if (source_size < result_size)

Re: [Patch, Fortran] PR 69495: unused-label warning does not tell which flag triggered it

On Wed, 3 Feb 2016, Manfred Schwarb wrote: > There are 2 things with translation, and there is a third issue: > - As you noticed, breaking things differently means translation has to be > done again. > - Normally, each string is translated independently, and depending on the > language there

Re: [Patch, Fortran] PR 69495: unused-label warning does not tell which flag triggered it

Hi, 2016-02-03 10:21 GMT+01:00 Manfred Schwarb : >> here is a diagnostics patch, which makes sure that the responsible >> flag is printed in several warning messages (for which this was still >> missing). >> > >if (source_size < result_size) > -gfc_warning (0, "Intrinsic

[Patch, Fortran] PR 69495: unused-label warning does not tell which flag triggered it

Hi all, here is a diagnostics patch, which makes sure that the responsible flag is printed in several warning messages (for which this was still missing). The only case that I'm not completely sure about is the hunk in intrinsic.c. In particular I was not able to trigger this warning and found