public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/98920] [10/11 Regression] uses regexec without support for REG_STARTEND with -fsanitize=address
Date: Tue, 09 Feb 2021 11:50:25 +0000	[thread overview]
Message-ID: <bug-98920-4-FKhQ3igmjv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98920-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from Martin Liška <marxin at gcc dot gnu.org> ---
On x86_64 these are intercepted from the list you provided:

sched_getaffinity
clock_getcpuclockid
lgammal
clock_settime
clock_gettime
memcpy
fmemopen
realpath
lgamma
lgammaf
glob
glob64
pthread_attr_getaffinity_np
pthread_sigmask
regexec
clock_getres

  parent reply	other threads:[~2021-02-09 11:50 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01 16:42 [Bug sanitizer/98920] New: " doko at debian dot org
2021-02-02  8:14 ` [Bug sanitizer/98920] " rguenth at gcc dot gnu.org
2021-02-02 10:04 ` marxin at gcc dot gnu.org
2021-02-02 12:52 ` marxin at gcc dot gnu.org
2021-02-04 11:08 ` jakub at gcc dot gnu.org
2021-02-04 11:19 ` jakub at gcc dot gnu.org
2021-02-05 12:39 ` marxin at gcc dot gnu.org
2021-02-05 13:07 ` jakub at gcc dot gnu.org
2021-02-05 13:16 ` fw at gcc dot gnu.org
2021-02-05 13:34 ` jakub at gcc dot gnu.org
2021-02-05 14:29 ` fw at gcc dot gnu.org
2021-02-05 14:41 ` jakub at gcc dot gnu.org
2021-02-09  9:33 ` marxin at gcc dot gnu.org
2021-02-09  9:35 ` marxin at gcc dot gnu.org
2021-02-09  9:54 ` jakub at gcc dot gnu.org
2021-02-09 11:50 ` marxin at gcc dot gnu.org [this message]
2021-02-26 12:40 ` rguenth at gcc dot gnu.org
2021-03-08 14:55 ` cvs-commit at gcc dot gnu.org
2021-03-08 14:56 ` marxin at gcc dot gnu.org
2021-03-09 10:47 ` ro at gcc dot gnu.org
2021-03-09 11:16 ` jakub at gcc dot gnu.org
2021-03-09 12:06 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-03-09 13:15 ` cvs-commit 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-98920-4-FKhQ3igmjv@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).