public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rafael at espindo dot la" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/94910] New: detect_stack_use_after_return=1 is much slower than clang's Date: Fri, 01 May 2020 20:51:52 +0000 [thread overview] Message-ID: <bug-94910-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94910 Bug ID: 94910 Summary: detect_stack_use_after_return=1 is much slower than clang's Product: gcc Version: 9.3.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: rafael at espindo dot la CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org Target Milestone: --- The test I am using is from https://github.com/scylladb/seastar/. It can be build with $ cmake -DCMAKE_BUILD_TYPE=Debug -GNinja <src> $ ninja tests/unit/chunked_fifo_test And can be run with: Clang: $ time ASAN_OPTIONS=detect_stack_use_after_return=1 ./tests/unit/chunked_fifo_test -t chunked_fifo_big ... 1.80s user 0.02s system 99% cpu 1.826 total $ time ASAN_OPTIONS=detect_stack_use_after_return=0 ./tests/unit/chunked_fifo_test -t chunked_fifo_big ... 1.67s user 0.01s system 99% cpu 1.691 total GCC: $ time ASAN_OPTIONS=detect_stack_use_after_return=1 ./tests/unit/chunked_fifo_test -t chunked_fifo_big 89.12s user 0.03s system 99% cpu 1:29.34 total $ time ASAN_OPTIONS=detect_stack_use_after_return=0 ./tests/unit/chunked_fifo_test -t chunked_fifo_big 1.32s user 0.02s system 99% cpu 1.350 total So while plain asan is faster with gcc, enabling detect_stack_use_after_return makes it much slower.
next reply other threads:[~2020-05-01 20:51 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-01 20:51 rafael at espindo dot la [this message] 2020-05-04 5:27 ` [Bug sanitizer/94910] " marxin at gcc dot gnu.org 2020-05-15 11:31 ` marxin at gcc dot gnu.org 2020-05-15 16:28 ` rafael at espindo dot la 2020-05-18 9:11 ` marxin at gcc dot gnu.org 2020-05-18 9:12 ` marxin at gcc dot gnu.org 2020-05-18 10:39 ` jakub at gcc dot gnu.org 2020-05-19 13:26 ` marxin at gcc dot gnu.org 2020-05-19 21:05 ` rafael at espindo dot la 2020-05-20 9:11 ` marxin at gcc dot gnu.org 2020-05-25 8:32 ` marxin at gcc dot gnu.org 2020-06-10 11:19 ` cvs-commit at gcc dot gnu.org 2020-06-10 11:20 ` marxin at gcc dot gnu.org 2020-06-12 8:03 ` cvs-commit at gcc dot gnu.org 2020-06-12 8:17 ` cvs-commit at gcc dot gnu.org 2020-06-12 8:30 ` cvs-commit at gcc dot gnu.org 2020-06-12 8:30 ` marxin 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-94910-4@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: linkBe 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).