This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran 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] PR41582 allocate patch for CLASS

From: Janus Weil <janus at gcc dot gnu dot org>
To: Paul Richard Thomas <paul dot richard dot thomas at gmail dot com>
Cc: Tobias Burnus <burnus at net-b dot de>, fortran at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
Date: Sat, 10 Oct 2009 23:40:28 +0200
Subject: Re: [Patch,Fortran] PR41582 allocate patch for CLASS
References: <20091009171151.GA25954@net-b.de> <854832d40910091226g8024b8evd0272227c7eb5e17@mail.gmail.com> <339c37f20910101321w71d2e944q5989671bebb21da1@mail.gmail.com>

>> 2) Add a 'size' field to the class container. Advantage: Cleaner code,
>> better performance. Downside: Larger class container. (Ideally this
>> field could be in the vtable, so that it does not need to be stored
>> for each class variable, but only once.)
>
> I would go for this one, for the time being. ?It has the advantage of
> considerable simplicity.

Agreed.


> Having read up a bit on the g++ implementation,

For those who have not done this kind of research: Could you share
your findings?


> PS Do you want to do it or shall I?

I can do it. Maybe you can take care of the TBP problems instead, e.g.
PR41556, PR41648 and PR41656.


Thanks,
Janus

References:
- [Patch,Fortran] PR41582 allocate patch for CLASS
  - From: Tobias Burnus
- Re: [Patch,Fortran] PR41582 allocate patch for CLASS
  - From: Janus Weil
- Re: [Patch,Fortran] PR41582 allocate patch for CLASS
  - From: Paul Richard Thomas

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