On 03/15/2012 11:42 AM, Janne Blomqvist wrote:
PING! (At this point, obviously for trunk only)
Yes, OK for trunk.
On Mon, Feb 13, 2012 at 20:20, Janne Blomqvist
wrote:
Hi,
the attached patch changes the low-level libgfortran IO dispatching
mechanism to use shared vtables for each stream
PING! (At this point, obviously for trunk only)
On Mon, Feb 13, 2012 at 20:20, Janne Blomqvist
wrote:
> Hi,
>
> the attached patch changes the low-level libgfortran IO dispatching
> mechanism to use shared vtables for each stream type, instead of all
> the function pointers being replicated for e
On Fri, Feb 17, 2012 at 12:44 PM, Janne Blomqvist
wrote:
> On Mon, Feb 13, 2012 at 23:04, Steven Bosscher wrote:
>> On Mon, Feb 13, 2012 at 7:20 PM, Janne Blomqvist
>> wrote:
>>> Hi,
>>>
>>> the attached patch changes the low-level libgfortran IO dispatching
>>> mechanism to use shared vtables f
On Mon, Feb 13, 2012 at 23:04, Steven Bosscher wrote:
> On Mon, Feb 13, 2012 at 7:20 PM, Janne Blomqvist
> wrote:
>> Hi,
>>
>> the attached patch changes the low-level libgfortran IO dispatching
>> mechanism to use shared vtables for each stream type, instead of all
>> the function pointers being
On Mon, Feb 13, 2012 at 7:20 PM, Janne Blomqvist
wrote:
> Hi,
>
> the attached patch changes the low-level libgfortran IO dispatching
> mechanism to use shared vtables for each stream type, instead of all
> the function pointers being replicated for each unit. This is similar
> to e.g. how the C++
Hi,
the attached patch changes the low-level libgfortran IO dispatching
mechanism to use shared vtables for each stream type, instead of all
the function pointers being replicated for each unit. This is similar
to e.g. how the C++ frontend implements vtables. The benefits are:
- Slightly smaller