Dear All,
> thanks for the review - and for the f95-lang.c patch. I have updated the
> patch to use calloc, build & regtested it, and committed it as Rev. 183247.
Good - I will go back to array allocation and use calloc there as well.
Cheers
Paul
Dear Janne, dear Paul,
thanks for the review - and for the f95-lang.c patch. I have updated the
patch to use calloc, build & regtested it, and committed it as Rev. 183247.
Tobias
2012-01-17 Tobias Burnus
Janne Blomqvist
PR fortran/51869
* trans-expr.c (alloc_scalar_a
On Tue, Jan 17, 2012 at 14:36, Janne Blomqvist
wrote:
> On Tue, Jan 17, 2012 at 14:29, Paul Richard Thomas
> wrote:
>> Dear Tobias and Janne,
>>
>> I had preparedand was about to submit the identical patch :-)
>>
>> On Tue, Jan 17, 2012 at 12:45 PM, Janne Blomqvist
>> wrote:
>>> On Tue, Jan 17,
On Tue, Jan 17, 2012 at 14:29, Paul Richard Thomas
wrote:
> Dear Tobias and Janne,
>
> I had preparedand was about to submit the identical patch :-)
>
> On Tue, Jan 17, 2012 at 12:45 PM, Janne Blomqvist
> wrote:
>> On Tue, Jan 17, 2012 at 13:24, Tobias Burnus wrote:
>>> This patch nullifies (sca
Dear Tobias and Janne,
I had preparedand was about to submit the identical patch :-)
On Tue, Jan 17, 2012 at 12:45 PM, Janne Blomqvist
wrote:
> On Tue, Jan 17, 2012 at 13:24, Tobias Burnus wrote:
>> This patch nullifies (scalar) allocatables after malloc, if (and only if)
>> they contain alloca
On Tue, Jan 17, 2012 at 13:24, Tobias Burnus wrote:
> This patch nullifies (scalar) allocatables after malloc, if (and only if)
> they contain allocatable components to make sure that no uninitialized
> memory is accessed.
>
> Build and regtested on x86-64-linux.
> OK for the trunk?
calloc potent
This patch nullifies (scalar) allocatables after malloc, if (and only
if) they contain allocatable components to make sure that no
uninitialized memory is accessed.
Build and regtested on x86-64-linux.
OK for the trunk?
Tobias
2012-01-17 Tobias Burnus
PR fortran/51869
* trans-expr.c (all
