Re: [Patch, fortran] PR39239 EQUIVALENCE and BIND(C)

Dear Nicolas, This is OK for trunk. Thanks for the patch. Paul On 19 March 2017 at 14:34, Nicolas Koenig wrote: > Hello Paul, > > there isn't really a reason for that except for not knowing where to put the > error. Attached are the new patch & test case. > > The

Re: [Patch, fortran] PR39239 EQUIVALENCE and BIND(C)

Hi Nicolas, Is there some reason that you didn't use symbol.c(check_conflict)? The conflict check could be added at line 547. If this results in repetitions of the error message, then your patch is OK. Otherwise, I would pop it in there. Do you have commit rights? ie. have you done the FSF

[Patch, fortran] PR39239 EQUIVALENCE and BIND(C)

Hello everyone, I submitted this patch a week ago, but I think it got lost. It adds an error if BIND(C) is used with EQUIVALENCE. Nicolas Regression tested for x86_64-pc-linux-gnu. 2017-03-18 Nicolas Koenig PR fortran/39239 *