On 12/08/2015 08:33 AM, Bernd Schmidt wrote:
On 12/08/2015 04:28 PM, Martin Liška wrote:
Majority of them (~2600 BTs) are in fortran FE (BT contains 'gfc_'): [2].
The rest contains some issues in CP FE, many GGC invalid read/write
operations ([4]) and many
memory leaks in gcc.c (for instance op
On 12/08/2015 04:28 PM, Martin Liška wrote:
Majority of them (~2600 BTs) are in fortran FE (BT contains 'gfc_'): [2].
The rest contains some issues in CP FE, many GGC invalid read/write operations
([4]) and many
memory leaks in gcc.c (for instance option handling).
My question is if a bug shou
On 12/03/2015 03:15 PM, Bernd Schmidt wrote:
> On 11/23/2015 10:34 AM, Martin Liška wrote:
>> On 11/21/2015 05:26 AM, Hans-Peter Nilsson wrote:
>>> IIRC you can replace the actual dg-runtest proc with your own
>>> (implementing a wrapper). Grep aroung, I think we do that
>>> already. That's certa
On 11/23/2015 10:34 AM, Martin Liška wrote:
On 11/21/2015 05:26 AM, Hans-Peter Nilsson wrote:
IIRC you can replace the actual dg-runtest proc with your own
(implementing a wrapper). Grep aroung, I think we do that
already. That's certainly preferable instead of touching all
callers.
You are
On Mon, 23 Nov 2015, Martin Li?ka wrote:
> On 11/21/2015 05:26 AM, Hans-Peter Nilsson wrote:
> > On Thu, 19 Nov 2015, Martin Li?ka wrote:
> >> Hello.
> >>
> >> In last two weeks I've removed couple of memory leaks, mainly tight to
> >> middle-end.
> >> Currently, a user of the GCC compiler can pas
On 11/21/2015 05:26 AM, Hans-Peter Nilsson wrote:
> On Thu, 19 Nov 2015, Martin Li?ka wrote:
>> Hello.
>>
>> In last two weeks I've removed couple of memory leaks, mainly tight to
>> middle-end.
>> Currently, a user of the GCC compiler can pass '--enable-checking=valgrind'
>> configure option
>>
On Thu, 19 Nov 2015, Martin Li?ka wrote:
> Hello.
>
> In last two weeks I've removed couple of memory leaks, mainly tight to
> middle-end.
> Currently, a user of the GCC compiler can pass '--enable-checking=valgrind'
> configure option
> that will run all commands within valgrind environment, but
On 2015.11.19 at 15:38 +0100, Martin Liška wrote:
>
> In last two weeks I've removed couple of memory leaks, mainly tight to
> middle-end. Currently, a user of the GCC compiler can pass
> '--enable-checking=valgrind' configure option that will run all
> commands within valgrind environment, but a
Hello.
In last two weeks I've removed couple of memory leaks, mainly tight to
middle-end.
Currently, a user of the GCC compiler can pass '--enable-checking=valgrind'
configure option
that will run all commands within valgrind environment, but as the valgrind
runs just with '-q' option,
the resu
