public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/98265] [10/11 Regression] gcc-10 has significantly worse code generated with -O2 compared to -O1 (or gcc-9 -O2) when using the Eigen C++ library Date: Tue, 12 Jan 2021 09:40:11 +0000 [thread overview] Message-ID: <bug-98265-4-tMtiLB0A8t@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98265-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98265 --- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> --- Created attachment 49947 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49947&action=edit Reduced test-case I reduced a test-case where GCC 10 does not inline all in fn called 'should_inline'.
next prev parent reply other threads:[~2021-01-12 9:40 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-13 23:11 [Bug ipa/98265] New: " kartikmohta at gmail dot com 2020-12-13 23:12 ` [Bug ipa/98265] " kartikmohta at gmail dot com 2021-01-04 14:29 ` [Bug ipa/98265] [10/11 Regression] " rguenth at gcc dot gnu.org 2021-01-11 21:47 ` kartikmohta at gmail dot com 2021-01-12 9:40 ` marxin at gcc dot gnu.org [this message] 2021-01-12 9:40 ` marxin at gcc dot gnu.org 2021-01-14 11:07 ` rguenth at gcc dot gnu.org 2021-02-14 22:47 ` hubicka at gcc dot gnu.org 2021-02-14 22:50 ` hubicka at gcc dot gnu.org 2021-03-31 20:45 ` cvs-commit at gcc dot gnu.org 2021-03-31 20:47 ` cvs-commit at gcc dot gnu.org 2021-04-01 10:12 ` cvs-commit at gcc dot gnu.org 2021-04-01 10:14 ` hubicka at gcc dot gnu.org 2021-04-09 10:42 ` [Bug ipa/98265] [10 " rguenth at gcc dot gnu.org 2021-04-09 12:01 ` rguenth at gcc dot gnu.org 2021-04-10 11:07 ` schwab@linux-m68k.org 2021-04-15 9:54 ` hubicka at gcc dot gnu.org 2021-09-05 17:54 ` 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-98265-4-tMtiLB0A8t@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).