public inbox for jit@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: David Malcolm <dmalcolm@redhat.com>,
	Marek Polacek <polacek@redhat.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>,
	jit@gcc.gnu.org
Subject: Re: [PATCH] use-after-scope fallout
Date: Fri, 01 Jan 2016 00:00:00 -0000	[thread overview]
Message-ID: <20161108121006.GU3541@tucnak.redhat.com> (raw)
In-Reply-To: <26e56fb7-f60f-4438-d118-e4346d43305c@suse.cz>

On Tue, Nov 08, 2016 at 01:00:19PM +0100, Martin Liška wrote:
> This is fallout fix where I changed:
> 
> 1) Fix ICE for lambda functions (added test-case: use-after-scope-4.C)
> 2) Fix ICE in gimplify_switch_expr, at gimplify.c:2269 (fixed by not adding
> artificial variables)
> 3) PR testsuite/78242 - I basically removed the test (not interesting)
> 4) LEAF and NOTHROW flags are properly set on ASAN {un}poison functions
> 5) dbg_cnt has been added
> 6) use-after-scope-types-4.C - scanned pattern is updated to work on i686
> 
> Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
> 
> Ready to be installed?
> Martin

> >From 36eb4a8b3542729c9c428ac319d8422bea677869 Mon Sep 17 00:00:00 2001
> From: marxin <mliska@suse.cz>
> Date: Mon, 7 Nov 2016 14:49:00 +0100
> Subject: [PATCH] use-after-scope fallout
> 
> gcc/testsuite/ChangeLog:
> 
> 2016-11-08  Martin Liska  <mliska@suse.cz>
> 
> 	PR testsuite/78242
> 	* g++.dg/asan/use-after-scope-4.C: New test.
> 	* g++.dg/asan/use-after-scope-types-4.C: Update scanned pattern.
> 	* gcc.dg/asan/use-after-scope-8.c: Remove.
> 
> gcc/ChangeLog:
> 
> 2016-11-08  Martin Liska  <mliska@suse.cz>
> 
> 	PR testsuite/78242
> 	* dbgcnt.def: Add new debug counter asan_use_after_scope.
> 	* gimplify.c (gimplify_decl_expr): Do not sanitize vars
> 	with a value expr.  Do not add artificial variables to
> 	live_switch_vars.  Use the debug counter.
> 	(gimplify_target_expr): Use the debug counter.
> 	* internal-fn.def: Remove ECF_TM_PURE from ASAN_MARK builtin.
> 	* sanitizer.def: Set ATTR_NOTHROW_LEAF_LIST to
> 	BUILT_IN_ASAN_CLOBBER_N and BUILT_IN_ASAN_UNCLOBBER_N.

Ok.  BTW, in stage3 please also check if/how nested functions (C and
fortran) work, I bet if you ASAN_MARK some vars and then
tree-nested.c moves them into an artificial struct that things might
not work 100% properly (e.g. would there be a guarantee that it is
unpoisoned upon function exit)?

	Jakub

      parent reply	other threads:[~2016-11-08 12:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20161027172358.GN3541@tucnak.redhat.com>
     [not found] ` <782727c2-9173-24ab-4e4c-07918dc16bf6@suse.cz>
     [not found]   ` <20161101145350.GS3541@tucnak.redhat.com>
     [not found]     ` <3f0181a4-e1b2-406f-7cf1-e63e9e9824fe@suse.cz>
     [not found]       ` <20161102095926.GM3541@tucnak.redhat.com>
     [not found]         ` <20161102101053.GN3541@tucnak.redhat.com>
     [not found]           ` <20161102142028.GQ5939@redhat.com>
     [not found]             ` <8ac49efe-83af-933b-2aa5-f4b22972fa6a@suse.cz>
     [not found]               ` <20161102143511.GV3541@tucnak.redhat.com>
     [not found]                 ` <e04b1ac8-e3ff-b13f-4006-bf961af6d2ea@suse.cz>
     [not found]                   ` <20161104093254.GS3541@tucnak.redhat.com>
     [not found]                     ` <0e0fd0f9-1c7d-ac9e-8dfc-9349611b5efe@suse.cz>
     [not found]                       ` <59fde5a4-3633-5fc8-daa0-ed485d75a5db@suse.cz>
2016-01-01  0:00                         ` Fix build of jit (was Re: [PATCH, RFC] Introduce -fsanitize=use-after-scope (v3)) David Malcolm
2016-01-01  0:00                           ` Jakub Jelinek
2016-01-01  0:00                             ` Martin Liška
2016-01-01  0:00                               ` Jakub Jelinek
2016-01-01  0:00                                 ` [PATCH] use-after-scope fallout Martin Liška
2016-01-01  0:00                                   ` David Malcolm
2016-01-01  0:00                                   ` Jakub Jelinek [this message]

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=20161108121006.GU3541@tucnak.redhat.com \
    --to=jakub@redhat.com \
    --cc=dmalcolm@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jit@gcc.gnu.org \
    --cc=mliska@suse.cz \
    --cc=polacek@redhat.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).