public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka 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: Sun, 14 Feb 2021 22:47:32 +0000 [thread overview]
Message-ID: <bug-98265-4-iYBiS3umBQ@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 #5 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
We do not inline CwiseNullaryOp because it uses comdat local symbols.
This is because we do split the function and the .part stays local.
At least we should recompute if function calls comdat local after comdat local
function is inlined.
IPA function summary for Eigen::Matrix<float, 3, 1> should_inline(float, float,
float, float)/2 inlinable fp_expression
global time: 36.000000
self size: 21
global size: 29
min size: 24
self stack: 16
global stack: 20
size:19.000000, time:18.500000
size:4.500000, time:3.500000, executed if:(not inlined)
calls:
operator*.isra/90 inlined
freq:1.00
Stack frame offset 16, callee self size 4
Eigen::CwiseNullaryOp< <template-parameter-1-1>, <template-parameter-1-2>
>::CwiseNullaryOp(long int, long int, Eigen::scalar_constant_op<float>) [with
<template-parameter-1-1> = Eigen::scalar_constant_op<float>; PlainObjectType =
Eigen::Matrix<float, 4, 5, 6, 4, 5>]/20 callee refers to comdat-local symbols
freq:1.00 loop depth: 0 size: 5 time: 14 callee size: 6 stack: 0
op0 is compile time invariant
op0 points to local or readonly memory
op1 is compile time invariant
op2 is compile time invariant
op2 points to local or readonly memory
next prev parent reply other threads:[~2021-02-14 22:47 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
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 [this message]
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-iYBiS3umBQ@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: link
Be 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).