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 r13-1343] libsanitizer: cherry-pick 791e0d1bc85d
Date: Wed, 29 Jun 2022 13:29:58 +0000 (GMT)	[thread overview]
Message-ID: <20220629132958.4F5BD3850227@sourceware.org> (raw)

https://gcc.gnu.org/g:aa87b7541b4c11f59c521154513f844ea6b5c977

commit r13-1343-gaa87b7541b4c11f59c521154513f844ea6b5c977
Author: Martin Liska <mliska@suse.cz>
Date:   Wed Jun 29 15:28:07 2022 +0200

    libsanitizer: cherry-pick 791e0d1bc85d
    
    791e0d1bc85d: [compiler-rt] Add NO_EXEC_STACK_DIRECTIVE on s390x

Diff:
---
 libsanitizer/tsan/tsan_rtl_s390x.S | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/libsanitizer/tsan/tsan_rtl_s390x.S b/libsanitizer/tsan/tsan_rtl_s390x.S
index fcff35fbc7e..2f445e8f1b2 100644
--- a/libsanitizer/tsan/tsan_rtl_s390x.S
+++ b/libsanitizer/tsan/tsan_rtl_s390x.S
@@ -45,3 +45,5 @@ intercept setjmp, _ZN14__interception11real_setjmpE
 intercept _setjmp, _ZN14__interception12real__setjmpE
 intercept sigsetjmp, _ZN14__interception14real_sigsetjmpE
 intercept __sigsetjmp, _ZN14__interception16real___sigsetjmpE
+
+NO_EXEC_STACK_DIRECTIVE


                 reply	other threads:[~2022-06-29 13:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220629132958.4F5BD3850227@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).