public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/112644] [14 Regression] Some of the hwasan testcase fail after the recent merge
Date: Wed, 31 Jan 2024 14:49:34 +0000	[thread overview]
Message-ID: <bug-112644-4-vpigAYEGZ7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112644-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112644

--- Comment #9 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tamar Christina <tnfchris@gcc.gnu.org>:

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

commit r14-8659-ga73421bcf301911f2cbdb1c58316ddf3473ea6d5
Author: Tamar Christina <tamar.christina@arm.com>
Date:   Wed Jan 31 14:44:35 2024 +0000

    libsanitizer: Sync fixes for asan interceptors from upstream

    This cherry-picks and squashes the differences between commits

   
d3e5c20ab846303874a2a25e5877c72271fc798b..76e1e45922e6709392fb82aac44bebe3dbc2ea63
    from LLVM upstream from compiler-rt/lib/hwasan/ to GCC on the changes
relevant
    for GCC.

    This is required to fix the linked PR.

    As mentioned in the PR the last sync brought in a bug from upstream[1]
where
    operations became non-recoverable and as such the tests in AArch64 started
    failing.  This cherry picks the fix and there are minor updates needed to
GCC
    after this to fix the cases.

    [1] https://github.com/llvm/llvm-project/pull/74000

    PR sanitizer/112644
    Cherry-pick llvm-project revision
    672b71cc1003533460a82f06b7d24fbdc02ffd58,
    5fcf3bbb1acfe226572474636714ede86fffcce8,
    3bded112d02632209bd55fb28c6c5c234c23dec3 and
    76e1e45922e6709392fb82aac44bebe3dbc2ea63.

  parent reply	other threads:[~2024-01-31 14:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-21  1:01 [Bug sanitizer/112644] New: " pinskia at gcc dot gnu.org
2023-11-21  1:01 ` [Bug sanitizer/112644] " pinskia at gcc dot gnu.org
2023-11-21  1:04 ` pinskia at gcc dot gnu.org
2023-11-21  1:10 ` pinskia at gcc dot gnu.org
2023-11-21 10:26 ` jakub at gcc dot gnu.org
2023-11-22 11:19 ` tnfchris at gcc dot gnu.org
2023-11-22 11:20 ` jakub at gcc dot gnu.org
2023-12-01 10:40 ` tnfchris at gcc dot gnu.org
2023-12-01 10:41 ` tnfchris at gcc dot gnu.org
2023-12-05 10:18 ` tnfchris at gcc dot gnu.org
2024-01-29 17:26 ` tnfchris at gcc dot gnu.org
2024-01-31 14:49 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-31 14:50 ` cvs-commit at gcc dot gnu.org
2024-01-31 14:52 ` cvs-commit at gcc dot gnu.org
2024-01-31 14:54 ` tnfchris at gcc dot gnu.org

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=bug-112644-4-vpigAYEGZ7@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).