From: Jakub Jelinek <jakub@redhat.com>
To: Richard Biener <rguenther@suse.de>
Cc: Dodji Seketeli <dodji@redhat.com>,
Yury Gribov <y.gribov@samsung.com>,
Jan Hubicka <hubicka@ucw.cz>,
Marek Polacek <polacek@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Optimize ASAN_CHECK checks
Date: Fri, 14 Nov 2014 13:06:00 -0000 [thread overview]
Message-ID: <20141114122822.GR5026@tucnak.redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1411141315580.374@zhemvz.fhfr.qr>
On Fri, Nov 14, 2014 at 01:16:36PM +0100, Richard Biener wrote:
> > That would be indeed nice (similarly for other stuff that we expect to be
> > undefined on pass boundaries, or expect to be in certain state at pass
> > boundaries; in the former case set before uses, and don't care about what
> > state we leave it in, in the latter case can assume some state first (say 0)
> > and have to put it back into the same state). There are various visited
> > flags and the like, Richard, any ideas what other things might be nice to
> > document?
>
> aux pointers on CFG structures which I believe have to be cleared
> after each pass that uses them (maybe already documented).
>
> Nothing else off the top of my head.
There is at least gimple_plf GF_PLF_{1,2} too, gimple_visited_p, BB_VISITED, ...
Jakub
next prev parent reply other threads:[~2014-11-14 12:28 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 14:28 [PATCH] Optimize UBSAN_NULL checks, add sanopt.c Marek Polacek
2014-11-03 15:35 ` Jakub Jelinek
2014-11-04 18:36 ` Marek Polacek
2014-11-04 19:18 ` Jakub Jelinek
2014-11-05 9:19 ` Yury Gribov
2014-11-05 9:33 ` Jakub Jelinek
2014-11-05 9:54 ` Yury Gribov
2014-11-05 10:29 ` Marek Polacek
2014-11-05 10:50 ` Jakub Jelinek
2014-11-05 11:23 ` Marek Polacek
2014-11-05 12:16 ` Yury Gribov
2014-11-05 12:22 ` Jakub Jelinek
2014-11-05 12:34 ` Yury Gribov
2014-11-05 13:13 ` Yury Gribov
2014-11-05 13:23 ` Jakub Jelinek
2014-11-05 13:48 ` Yury Gribov
2014-11-12 9:52 ` Maxim Ostapenko
2014-11-12 10:11 ` Jakub Jelinek
2014-11-12 11:54 ` Maxim Ostapenko
2014-11-12 22:53 ` [PATCH] Propagate nonfreeing_call_p using ipa-pure-const Jakub Jelinek
2014-11-12 23:11 ` Jan Hubicka
2014-11-13 7:45 ` Jakub Jelinek
2014-11-13 8:44 ` [PATCH] Propagate nonfreeing_call_p using ipa-pure-const (take 2) Jakub Jelinek
2014-11-13 11:08 ` Richard Biener
2014-11-13 12:05 ` Jakub Jelinek
2014-11-14 17:44 ` Jakub Jelinek
2014-11-14 17:51 ` Jan Hubicka
2014-11-11 17:49 ` [RFC PATCH] Optimize ASAN_CHECK checks Jakub Jelinek
2014-11-12 9:26 ` Yury Gribov
2014-11-12 10:35 ` Jakub Jelinek
2014-11-12 11:12 ` Yury Gribov
2014-11-12 22:41 ` [PATCH] " Jakub Jelinek
2014-11-14 11:31 ` Dodji Seketeli
2014-11-14 12:02 ` Jakub Jelinek
2014-11-14 12:16 ` Dodji Seketeli
2014-11-14 12:18 ` Jakub Jelinek
2014-11-14 12:28 ` Richard Biener
2014-11-14 13:06 ` Jakub Jelinek [this message]
2014-11-14 17:30 ` Jakub Jelinek
2014-11-25 17:26 ` [PATCH] Enhance ASAN_CHECK optimization Yury Gribov
2014-11-26 9:59 ` Jakub Jelinek
2014-11-26 18:43 ` ygribov
2014-11-26 18:50 ` Jakub Jelinek
2014-11-26 18:54 ` ygribov
2014-11-26 19:00 ` Jakub Jelinek
2014-12-03 8:09 ` [PATCHv2] " Yury Gribov
2014-12-03 8:36 ` Jakub Jelinek
2014-12-03 9:04 ` Yury Gribov
2014-12-03 9:07 ` Jakub Jelinek
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=20141114122822.GR5026@tucnak.redhat.com \
--to=jakub@redhat.com \
--cc=dodji@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=polacek@redhat.com \
--cc=rguenther@suse.de \
--cc=y.gribov@samsung.com \
/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).