From: Jeff Law <law@redhat.com>
To: "Bernd Schmidt" <bschmidt@redhat.com>,
"Martin Liška" <mliska@suse.cz>,
"Hans-Peter Nilsson" <hp@bitrange.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH,RFC] Introduce RUN_UNDER_VALGRIND in test-suite
Date: Tue, 08 Dec 2015 16:04:00 -0000 [thread overview]
Message-ID: <5666FF9A.2010306@redhat.com> (raw)
In-Reply-To: <5666F843.9000004@redhat.com>
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 option handling).
>>
>> My question is if a bug should be created for all fortran issues and
>> whether it's realistic that
>> they can be eventually fixed in next stage1?
>
> It hardly seems worthwhile to file a bug for every issue, that's just
> unnecessary bureaucracy. Fix them as you go along would be my
> recommendation, that probably takes a similar amount of time.
Agreed, let's just fix them as we go along.
Suppressions should be a last resort in those cases where the code is
operating correctly. It does happen here and there.
jeff
next prev parent reply other threads:[~2015-12-08 16:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 14:38 Martin Liška
2015-11-19 15:07 ` Markus Trippelsdorf
2015-11-21 4:44 ` Hans-Peter Nilsson
2015-11-23 9:36 ` Martin Liška
2015-11-24 9:17 ` Hans-Peter Nilsson
2015-12-03 14:15 ` Bernd Schmidt
2015-12-08 15:28 ` Martin Liška
2015-12-08 15:33 ` Bernd Schmidt
2015-12-08 16:04 ` Jeff Law [this message]
2016-05-13 13:04 ` RUN_UNDER_VALGRIND statistics for GCC 7 Martin Liška
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5666FF9A.2010306@redhat.com \
--to=law@redhat.com \
--cc=bschmidt@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hp@bitrange.com \
--cc=mliska@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).