public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "haoxintu at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/95807] GCC accepts "void value not ignored as it ought to be" in function template Date: Mon, 22 Jun 2020 13:59:21 +0000 [thread overview] Message-ID: <bug-95807-4-SC8DryX9pl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95807-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95807 --- Comment #6 from Haoxin Tu <haoxintu at gmail dot com> --- (In reply to Jonathan Wakely from comment #5) > What practical impact does this have on any real world code? > Why should we spend time on that, rather than the million other things we > have to fix? Hi, Jonathan, This is the question I am always thinking about. GCC is a big software somehow, and that's impossible to treat every part equally when it has issues. > Obviously in an ideal world GCC would be perfect, but the majority of your > bug reports are asking for time to be spent on things that just don't matter. My team nowadays are focusing on improving the quality of mature compilers. We just developed a tool to test them and then found those bugs. Our method might not perfect now and it only found some issues in FE, and we are designing a more effective approach to focus on the ME or BE parts (those parts might more important for GCC), it still needs some time for us. So I totally agree with that you said, and maybe later reports will be more useful for you. > If you really want it fixed, you can always do it yourself: > https://gcc.gnu.org/contribute.html This is a really constructive suggestion for me. I will try to do this at some time. Anyway, thanks for your kind and helpful response!
next prev parent reply other threads:[~2020-06-22 13:59 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-22 3:21 [Bug c++/95807] New: " haoxintu at gmail dot com 2020-06-22 3:24 ` [Bug c++/95807] " pinskia at gcc dot gnu.org 2020-06-22 3:48 ` haoxintu at gmail dot com 2020-06-22 9:46 ` redi at gcc dot gnu.org 2020-06-22 10:01 ` haoxintu at gmail dot com 2020-06-22 13:06 ` redi at gcc dot gnu.org 2020-06-22 13:59 ` haoxintu at gmail dot com [this message] 2020-06-22 15:47 ` redi at gcc dot gnu.org 2021-12-14 5:36 ` pinskia 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-95807-4-SC8DryX9pl@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).