This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [Patch, fortran] Rename gfc_code's expr4 field

From: Mikael Morin <mikael dot morin at sfr dot fr>
To: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
Cc: gcc-patches <gcc-patches at gcc dot gnu dot org>, gfortran <fortran at gcc dot gnu dot org>
Date: Wed, 5 Aug 2015 22:53:29 +0200
Subject: Re: [Patch, fortran] Rename gfc_code's expr4 field
Authentication-results: sourceware.org; auth=none
Authentication-results: sfrmc.priv.atos.fr; dkim=none (no signature); dkim-adsp=none (no policy) header dot from=mikael dot morin at sfr dot fr
References: <55C25BDD dot 3080408 at sfr dot fr> <20150805192455 dot GA25590 at troutmask dot apl dot washington dot edu>

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/acquired_lock should suffice.

Well, I plan to move the other LOCK/UNLOCK arguments there, and I willneed the struct to pack them together.


Mikael

Follow-Ups:
- Re: [Patch, fortran] Rename gfc_code's expr4 field
  - From: Steve Kargl

References:
- [Patch, fortran] Rename gfc_code's expr4 field
  - From: Mikael Morin
- Re: [Patch, fortran] Rename gfc_code's expr4 field
  - From: Steve Kargl

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]