public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gabravier at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/94919] Failure to recognize max pattern Date: Mon, 18 May 2020 08:54:00 +0000 [thread overview] Message-ID: <bug-94919-4-N5WgkV24mo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94919-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94919 --- Comment #2 from Gabriel Ravier <gabravier at gmail dot com> --- Essentially, what I've been doing in my spare time for the past few weeks is looking at random pieces of code all over the internet, looking at the results trunk gcc/clang give (usually on x86-64 (though I've been thinking about looking at arm and other architectures), with flags like -Ofast -march=tigerlake) and seeing whether GCC or LLVM optimizes them better than the other (and making appropriate bug reports). Some of these are from actual projects, some are from websites listing bithacks, some are from books like Hacker's Delight, some were written by myself when studying the code from those above sources, and finally a few of them were from testsuites in either LLVM or GCC (though those are rarer, especially for LLVM, since it takes time to convert them from LLVM bytecode to something I can compile with both GCC and Clang). For this particular bug report, I believe this is *probably* from somewhere in Hacker's Delight.
next prev parent reply other threads:[~2020-05-18 8:54 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-02 9:51 [Bug tree-optimization/94919] New: " gabravier at gmail dot com 2020-05-02 11:43 ` [Bug tree-optimization/94919] " glisse at gcc dot gnu.org 2020-05-18 8:54 ` gabravier at gmail dot com [this message] 2020-05-25 2:28 ` pinskia at gcc dot gnu.org 2020-08-10 0:53 ` gabravier at gmail 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-94919-4-N5WgkV24mo@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).