public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rvmallad at amazon dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/107409] Perf loss ~5% on 519.lbm_r SPEC cpu2017 benchmark Date: Wed, 26 Oct 2022 09:20:04 +0000 [thread overview] Message-ID: <bug-107409-4-Gmh2XRgTj3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107409-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107409 --- Comment #1 from Rama Malladi <rvmallad at amazon dot com> --- $ /home/ubuntu/gccfixissue1/bin/gcc -v Using built-in specs. COLLECT_GCC=/home/ubuntu/gccfixissue1/bin/gcc COLLECT_LTO_WRAPPER=/home/ubuntu/gccfixissue1/libexec/gcc/aarch64-unknown-linux-gnu/13.0.0/lto-wrapper Target: aarch64-unknown-linux-gnu Configured with: ../configure --prefix=/home/ubuntu/gccfixissue1 --enable-languages=c,fortran Thread model: posix Supported LTO compression algorithms: zlib gcc version 13.0.0 20221021 (experimental) (GCC)
next prev parent reply other threads:[~2022-10-26 9:20 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-26 9:05 [Bug tree-optimization/107409] New: " rvmallad at amazon dot com 2022-10-26 9:20 ` rvmallad at amazon dot com [this message] 2022-10-27 8:08 ` [Bug tree-optimization/107409] " marxin at gcc dot gnu.org 2022-10-27 8:13 ` marxin at gcc dot gnu.org 2022-10-27 8:15 ` rvmallad at amazon dot com 2022-10-27 8:28 ` marxin at gcc dot gnu.org 2022-10-27 12:08 ` rvmallad at amazon dot com 2022-10-27 12:18 ` mark at gcc dot gnu.org 2022-10-27 12:21 ` rvmallad at amazon dot com 2022-12-01 6:54 ` [Bug tree-optimization/107409] Perf loss ~5% on 519.lbm_r SPEC cpu2017 benchmark with r10-5090-ga9a4edf0e71bba rvmallad at amazon dot com 2022-12-01 10:09 ` marxin at gcc dot gnu.org 2022-12-08 10:32 ` rvmallad at amazon dot com 2022-12-09 9:48 ` rvmallad at amazon dot com 2022-12-09 10:05 ` marxin at gcc dot gnu.org 2022-12-12 9:48 ` rvmallad at amazon dot com 2023-01-09 4:38 ` rvmallad at amazon dot com 2023-01-09 8:41 ` marxin at gcc dot gnu.org 2023-01-30 18:15 ` jamborm at gcc dot gnu.org 2023-02-02 21:35 ` spop at gcc dot gnu.org 2023-02-03 2:00 ` rvmallad at amazon dot com 2023-02-20 3:57 ` rvmallad at amazon dot com 2023-02-24 10:26 ` rvmallad at amazon dot com 2023-03-30 4:56 ` rvmallad at amazon dot com 2023-03-30 4:58 ` rvmallad at amazon dot com 2023-03-30 7:52 ` marxin 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-107409-4-Gmh2XRgTj3@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).