On Wed, Aug 05, 2015 at 10:53:29PM +0200, Mikael Morin wrote:
> Le 05/08/2015 21:24, Steve Kargl a écrit :
> > On Wed, Aug 05, 2015 at 08:54:21PM +0200, Mikael Morin wrote:
> >>
> >> +/* LOCK/UNLOCK statements */
> >> +struct
> >> +{
> >> + gfc_expr *acquired_lock;
> >> +}
> >
Le 05/08/2015 21:24, Steve Kargl a écrit :
On Wed, Aug 05, 2015 at 08:54:21PM +0200, Mikael Morin wrote:
+/* LOCK/UNLOCK statements */
+struct
+{
+ gfc_expr *acquired_lock;
+}
+lock;
Just curious. Why add a struct with a single member?
I would have thought s/expr4/a
On Wed, Aug 05, 2015 at 08:54:21PM +0200, Mikael Morin wrote:
>
> this renames the expr4 field of gfc_code to the more descriptive
> ext.lock.acquired_lock.
> Regression tested on x86_64-unkown-linux-gnu. OK for trunk?
>
I don't have a problem with a name change.
> +/* LOCK/UNLOCK stateme
Hello,
this renames the expr4 field of gfc_code to the more descriptive
ext.lock.acquired_lock.
Regression tested on x86_64-unkown-linux-gnu. OK for trunk?
Mikael
2015-08-05 Mikael Morin
* gfortran.h (struct gfc_code): Move expr4 field to
ext.lock.acquired_lock.
*
