public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redbeard0531 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/99339] Poor codegen with simple varargs Date: Tue, 02 Mar 2021 13:28:05 +0000 [thread overview] Message-ID: <bug-99339-4-CKeBvVFKc0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99339-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99339 --- Comment #5 from Mathias Stearn <redbeard0531 at gmail dot com> --- I filed a related bug with clang right after this one if anyone want to follow along https://bugs.llvm.org/show_bug.cgi?id=49395. Just because clang does worse doesn't mean gcc shouldn't do better ;)
next prev parent reply other threads:[~2021-03-02 13:28 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-02 11:49 [Bug c/99339] New: " redbeard0531 at gmail dot com 2021-03-02 12:44 ` [Bug middle-end/99339] " rguenth at gcc dot gnu.org 2021-03-02 12:46 ` rguenth at gcc dot gnu.org 2021-03-02 12:53 ` rguenth at gcc dot gnu.org 2021-03-02 13:11 ` jakub at gcc dot gnu.org 2021-03-02 13:28 ` redbeard0531 at gmail dot com [this message] 2021-03-02 15:30 ` redbeard0531 at gmail dot com 2021-03-03 7:28 ` rguenth at gcc dot gnu.org 2021-03-03 8:41 ` jakub 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-99339-4-CKeBvVFKc0@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).