From: Jakub Jelinek <jakub@redhat.com>
To: Richard Biener <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH][RFC] location and BLOCK checker
Date: Thu, 10 Jan 2013 15:43:00 -0000 [thread overview]
Message-ID: <20130110154329.GC7269@tucnak.redhat.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1301101634280.6889@zhemvz.fhfr.qr>
On Thu, Jan 10, 2013 at 04:36:26PM +0100, Richard Biener wrote:
>
> The following is what I use to track down PR55792 - it adds verification
> that the GIMPLE IL only contains references to BLOCKs that are part
> of the functions BLOCK tree. Otherwise BLOCKs lack a reference that is
> seen by the garbage collector and funny things can happen.
>
> It probably should also scan DEBUG_STMTs.
>
> Do we want this in trunk or should it wait for stage1?
I'd say we want it in the trunk now (well, as soon as it doesn't report
regressions during bootstrap/regtest). And yes, it should check also
DEBUG_STMTs, eventhough for now we completely ignore their locations.
Jakub
next prev parent reply other threads:[~2013-01-10 15:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 15:38 Richard Biener
2013-01-10 15:43 ` Jakub Jelinek [this message]
2013-01-10 16:02 ` Richard Biener
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=20130110154329.GC7269@tucnak.redhat.com \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
/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).