On 19/04/2012 14:02, Tobias Burnus wrote:
> Updated patch enclosed.
>
> On 02/14/2012 12:42 PM, Tobias Burnus wrote:
>> in order to gain an overview for our code whether the recent RESHAPE
>> (and friends) bug affects us and to determine for which assignment a
>> reallocation happens, useful to mi
Updated patch enclosed.
On 02/14/2012 12:42 PM, Tobias Burnus wrote:
in order to gain an overview for our code whether the recent RESHAPE
(and friends) bug affects us and to determine for which assignment a
reallocation happens, useful to mitigate performance issues, I added
-Wrealloc-lhs and
Hello,
On Tuesday 14 February 2012 12:42:21 Tobias Burnus wrote:
> Fortunately, -O0 is often sufficient to remove the reallocation code.
>
I guess you mean -O1 here...
> In turn, the warning might be printed even if at the end no realloc code is
> generated or present with -O1.
>
Can it be ca
Hi all,
in order to gain an overview for our code whether the recent RESHAPE
(and friends) bug affects us and to determine for which assignment a
reallocation happens, useful to mitigate performance issues, I added
-Wrealloc-lhs and -Wrealloc-lhs-all.
The flag -Wrealloc-lhs is the more usefu
