public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug plugins/105171] gcc/toplev.c: `local_tick` can overflow and become -1 Date: Wed, 06 Apr 2022 08:16:31 +0000 [thread overview] Message-ID: <bug-105171-4-sPHB4246VH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105171-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105171 --- Comment #10 from Andrew Pinski <pinskia at gcc dot gnu.org> --- What is interesting here is any change will always going to be gcc 13+. So requiring gcc 4.6+ is not a bad thing. Gcc 12 does not even compile with gcc 4.7 or before now with the requirement of c++11. Gcc 4.8 was released over 9 years ago. Gcc 4.6 was 11 years ago. So supporting a 11 year old compiler for plugin is not realistic at this point really.
next prev parent reply other threads:[~2022-04-06 8:16 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-05 22:37 [Bug driver/105171] New: " jason at zx2c4 dot com 2022-04-05 22:52 ` [Bug driver/105171] gcc/toplev.c: " jason at zx2c4 dot com 2022-04-05 23:02 ` [Bug plugins/105171] " pinskia at gcc dot gnu.org 2022-04-05 23:02 ` pinskia at gcc dot gnu.org 2022-04-05 23:06 ` jason at zx2c4 dot com 2022-04-06 5:44 ` pinskia at gcc dot gnu.org 2022-04-06 7:10 ` pageexec at gmail dot com 2022-04-06 7:26 ` pinskia at gcc dot gnu.org 2022-04-06 7:50 ` jakub at gcc dot gnu.org 2022-04-06 8:01 ` pageexec at gmail dot com 2022-04-06 8:16 ` pinskia at gcc dot gnu.org [this message] 2022-04-06 8:22 ` jakub at gcc dot gnu.org 2022-04-06 8:34 ` pageexec at gmail dot com 2022-04-06 8:37 ` jakub at gcc dot gnu.org 2022-04-06 8:59 ` pageexec at gmail dot com 2022-04-06 22:46 ` jason at zx2c4 dot com 2022-04-06 22:52 ` pinskia at gcc dot gnu.org 2022-04-06 23:02 ` pinskia at gcc dot gnu.org 2022-04-06 23:11 ` jason at zx2c4 dot com 2022-04-06 23:13 ` pinskia at gcc dot gnu.org 2022-04-07 13:01 ` rguenth at gcc dot gnu.org 2022-04-14 12:18 ` jason at zx2c4 dot com 2022-04-14 13:22 ` jakub at gcc dot gnu.org 2022-04-19 19:15 ` jason at zx2c4 dot com
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-105171-4-sPHB4246VH@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).