public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/105559] [9/10/11/12 Regression] -g and -O3 cause timeout since r12-156-g8d4c374c4419a875 Date: Wed, 11 May 2022 15:46:32 +0000 [thread overview] Message-ID: <bug-105559-4-lh1U8R5VhR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105559-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105559 --- Comment #7 from David Binderman <dcb314 at hotmail dot com> --- Thanks for the fast work. Less than 2.5 hours from reported to fixed for a bug that hadn't been found for a couple of years. I should also mention that this bug was produced from code produced by csmith, a most excellent C source code generator program. There is a school of thought that says running csmith regularly over the gcc trunk will find bugs.
next prev parent reply other threads:[~2022-05-11 15:46 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-11 10:16 [Bug debug/105559] New: -g and -O3 cause timeout dcb314 at hotmail dot com 2022-05-11 10:31 ` [Bug c/105559] " dcb314 at hotmail dot com 2022-05-11 10:41 ` [Bug c/105559] [12/13 Regression] -g and -O3 cause timeout since r12-156-g8d4c374c4419a875 marxin at gcc dot gnu.org 2022-05-11 11:06 ` rguenth at gcc dot gnu.org 2022-05-11 11:34 ` [Bug rtl-optimization/105559] " rguenth at gcc dot gnu.org 2022-05-11 11:40 ` rguenth at gcc dot gnu.org 2022-05-11 12:34 ` cvs-commit at gcc dot gnu.org 2022-05-11 12:59 ` [Bug rtl-optimization/105559] [9/10/11/12 " rguenth at gcc dot gnu.org 2022-05-11 15:46 ` dcb314 at hotmail dot com [this message] 2022-05-12 6:47 ` rguenther at suse dot de 2022-05-19 12:47 ` cvs-commit at gcc dot gnu.org 2022-05-19 14:03 ` [Bug rtl-optimization/105559] [9/10/11 " cvs-commit at gcc dot gnu.org 2022-05-27 9:48 ` [Bug rtl-optimization/105559] [10 " rguenth at gcc dot gnu.org 2022-05-27 13:15 ` cvs-commit at gcc dot gnu.org 2022-05-27 13:15 ` rguenth 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-105559-4-lh1U8R5VhR@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).