public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/marxin/heads/libsanitizer-merge-v4)] libsanitizer: update test that mixes fake and real stack
Date: Tue,  3 May 2022 11:02:06 +0000 (GMT)	[thread overview]
Message-ID: <20220503110206.C34AB3858413@sourceware.org> (raw)

https://gcc.gnu.org/g:0b3e9b47c1d9a1a5f25814419493ed3b5e6042d5

commit 0b3e9b47c1d9a1a5f25814419493ed3b5e6042d5
Author: Martin Liska <mliska@suse.cz>
Date:   Mon May 2 13:58:49 2022 +0200

    libsanitizer: update test that mixes fake and real stack
    
    gcc/testsuite/ChangeLog:
    
            * c-c++-common/asan/alloca_loop_unpoisoning.c: Do not combine
            fake and real stack.

Diff:
---
 gcc/testsuite/c-c++-common/asan/alloca_loop_unpoisoning.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/gcc/testsuite/c-c++-common/asan/alloca_loop_unpoisoning.c b/gcc/testsuite/c-c++-common/asan/alloca_loop_unpoisoning.c
index 3050d3ba94b..86f0ce6d8a0 100644
--- a/gcc/testsuite/c-c++-common/asan/alloca_loop_unpoisoning.c
+++ b/gcc/testsuite/c-c++-common/asan/alloca_loop_unpoisoning.c
@@ -1,5 +1,6 @@
 /* { dg-do run } */
 /* { dg-require-effective-target alloca } */
+/* { dg-options "--param=asan-use-after-return=0" } */
 
 /* This testcase checks that allocas and VLAs inside loop are correctly unpoisoned.  */


             reply	other threads:[~2022-05-03 11:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03 11:02 Martin Liska [this message]
2022-05-03 12:24 Martin Liska

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=20220503110206.C34AB3858413@sourceware.org \
    --to=marxin@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    /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).