public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "qrzhang at gatech dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/108880] New: slow compilation with "-fsanitize=undefined" Date: Wed, 22 Feb 2023 06:41:52 +0000 [thread overview] Message-ID: <bug-108880-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108880 Bug ID: 108880 Summary: slow compilation with "-fsanitize=undefined" Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu 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: --- gcc-10 works fine. $ time gcc-10 -fsanitize=undefined abc.c real 0m0.081s $ time gcc-11 -fsanitize=undefined abc.c real 0m7.045s $ time gcc-trunk -fsanitize=undefined abc.c real 0m10.346s $ gcc-trunk -v gcc version 13.0.1 20230218 (experimental) [master r13-6132-g32b5875c911] (GCC) $ cat abc.c long a; short b, e; char c; int d, f, g; void h() { int i; f &= i ^= (((g &= 0 / d / d % 8 << 0 << 2) % a >> e) / c >> b) / 1 % 8 << 3; } void main() {}
next reply other threads:[~2023-02-22 6:41 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-22 6:41 qrzhang at gatech dot edu [this message] 2023-02-22 6:51 ` [Bug sanitizer/108880] [11/12/13 Regression] " pinskia at gcc dot gnu.org 2023-02-22 6:53 ` pinskia at gcc dot gnu.org 2023-02-22 6:54 ` pinskia at gcc dot gnu.org 2023-02-22 7:12 ` pinskia at gcc dot gnu.org 2023-02-22 10:25 ` [Bug c/108880] " rguenth at gcc dot gnu.org 2023-02-22 10:25 ` rguenth at gcc dot gnu.org 2023-02-22 15:41 ` mpolacek at gcc dot gnu.org 2023-02-22 15:51 ` mpolacek at gcc dot gnu.org 2023-02-22 16:16 ` mpolacek at gcc dot gnu.org 2023-02-22 18:24 ` mpolacek at gcc dot gnu.org 2023-02-22 19:46 ` mpolacek at gcc dot gnu.org 2023-02-22 19:48 ` jakub at gcc dot gnu.org 2023-02-22 19:50 ` mpolacek at gcc dot gnu.org 2023-02-22 20:06 ` jakub at gcc dot gnu.org 2023-02-22 20:14 ` mpolacek at gcc dot gnu.org 2023-02-22 20:46 ` jakub at gcc dot gnu.org 2023-02-22 20:51 ` mpolacek at gcc dot gnu.org 2023-02-22 22:47 ` cvs-commit at gcc dot gnu.org 2023-02-22 22:48 ` [Bug c/108880] [11/12 " mpolacek at gcc dot gnu.org 2023-03-04 18:02 ` cvs-commit at gcc dot gnu.org 2023-03-07 17:45 ` [Bug c/108880] [11 " mpolacek 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-108880-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).