public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/108880] [11/12/13 Regression] slow compilation with "-fsanitize=undefined" Date: Wed, 22 Feb 2023 15:41:06 +0000 [thread overview] Message-ID: <bug-108880-4-gI8GcSDZ0h@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108880-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108880 Marek Polacek <mpolacek at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mpolacek at gcc dot gnu.org --- Comment #5 from Marek Polacek <mpolacek at gcc dot gnu.org> --- Started with r11-3299: commit cba079f354a55363916759f6f186f92c5616b98a Author: Sandra Loosemore <sandra@codesourcery.com> Date: Sat Sep 19 07:32:35 2020 -0700 Move loop and switch tree data structures from cp/ to c-family/. This patch moves the definitions for DO_STMT, FOR_STMT, WHILE_STMT, SWITCH_STMT, BREAK_STMT, and CONTINUE_STMT from the C++ front end to c-family. This includes the genericizers, pretty-printers, and dump support as well as the tree definitions and accessors. Some related code for OMP_FOR and similar OMP constructs is also moved.
next prev parent reply other threads:[~2023-02-22 15:41 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-22 6:41 [Bug sanitizer/108880] New: " qrzhang at gatech dot edu 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 [this message] 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-gI8GcSDZ0h@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).