public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "matmal01 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/101744] [12 regression] hwasan new failures since r12-2424
Date: Thu, 05 Aug 2021 16:44:01 +0000	[thread overview]
Message-ID: <bug-101744-4-1snkhZqd4R@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101744-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Matthew Malcomson <matmal01 at gcc dot gnu.org> ---
Hi there,

I didn't check all the new tests that Christophe mentioned, but all those I
checked had `dg-require-effective-target hwaddress_exec` in them.

The test that determines that effective target should only pass with a modern
enough kernel (one that supports passing tagged pointers to its syscalls).
It is still failing on my native AArch64 machine.

For anyone that is seeing them -- what kernel version are you running?
If your kernel has not changed could you manually run the check and see if it
passes and why?

I've unfortunately lost my testing environment.  I'm working on getting it back
but will be a while before I can see if I can reproduce the failures on a
machine with the required kernel.

  parent reply	other threads:[~2021-08-05 16:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-03  9:23 [Bug sanitizer/101744] New: " clyon at gcc dot gnu.org
2021-08-03  9:37 ` [Bug sanitizer/101744] " schwab@linux-m68k.org
2021-08-03 10:46 ` rguenth at gcc dot gnu.org
2021-08-03 12:26 ` marxin at gcc dot gnu.org
2021-08-04  7:08 ` crazylht at gmail dot com
2021-08-04 12:51 ` crazylht at gmail dot com
2021-08-04 14:10 ` marxin at gcc dot gnu.org
2021-08-05  1:09 ` crazylht at gmail dot com
2021-08-05 16:44 ` matmal01 at gcc dot gnu.org [this message]
2021-12-19 17:06 ` pinskia at gcc dot gnu.org
2022-03-08 14:08 ` rguenth 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-101744-4-1snkhZqd4R@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).