public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/45572] [4.6 Regression] various ICEs with -finline-small-functions -findirect-inlining -finline-functions
Date: Tue, 07 Sep 2010 00:39:00 -0000	[thread overview]
Message-ID: <20100907003928.30019.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45572-14164@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from zsojka at seznam dot cz  2010-09-07 00:39 -------
Created an attachment (id=21724)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21724&action=view)
semi-reduced testcase 3

$ gcc -finline-small-functions -findirect-inlining -finline-functions -O1
pr45572-3.C 
pr45572-3.C:61:1: error: inlined_to pointer set for noninline callers
virtual _knumber* _knumfloat::add(const _knumber&) const/15(-1) @0x7f6fec4cdac0
(asm: _ZNK10_knumfloat3addERK8_knumber) (inline copy in virtual _knumber*
_knumfloat::add(const _knumber&) const/4) (clone of virtual _knumber*
_knumfloat::add(const _knumber&) const/4) availability:local analyzed 47 time,
16 benefit (48 after inlining) 28 size, 9 benefit (66 after inlining) 16 bytes
stack usage body local finalized inlinable
  called by: virtual _knumber* _knumfloat::add(const _knumber&) const/10 (0.03
per call) (indirect_inlining) (can throw external) 
  calls: virtual _knumber::NumType _knumfloat::type() const/6
(indirect_inlining) (0.03 per call) (nested in 5 loops) (can throw external)
virtual _knumber* _knumfloat::add(const _knumber&) const/25 (inlined)
(indirect_inlining) (0.01 per call) (nested in 5 loops) (can throw external)
virtual _knumfloat::operator long int() const/3 (indirect_inlining) (0.02 per
call) (nested in 5 loops) (can throw external) virtual _knumber*
_knumfloat::add(const _knumber&) const/26 (inlined) (0.02 per call) (nested in
5 loops) (can throw external) _knumfloat::_knumfloat(double)/5 (0.02 per call)
(nested in 5 loops) (can throw external) 
  References: 
  Refering this function: 
pr45572-3.C:61:1: internal compiler error: verify_cgraph_node failed
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.

Tested revisions:
r163921 - crash
r161659 - crash
r161170 - OK


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45572


  parent reply	other threads:[~2010-09-07  0:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-07  0:33 [Bug tree-optimization/45572] New: " zsojka at seznam dot cz
2010-09-07  0:35 ` [Bug tree-optimization/45572] " zsojka at seznam dot cz
2010-09-07  0:37 ` zsojka at seznam dot cz
2010-09-07  0:39 ` zsojka at seznam dot cz [this message]
2010-09-07  8:40 ` rguenth at gcc dot gnu dot org
2010-09-20 18:51 ` jamborm at gcc dot gnu dot org
2010-09-21 13:51 ` rguenth at gcc dot gnu dot org
2010-09-21 17:14 ` jamborm at gcc dot gnu dot org
2010-09-21 17:19 ` jamborm at gcc dot gnu dot org
2010-09-22  9:52 ` jamborm at gcc dot gnu dot org
     [not found] <bug-45572-4@http.gcc.gnu.org/bugzilla/>
2010-10-04 10:15 ` jamborm at gcc dot gnu.org
2010-11-03 16:30 ` rguenth 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=20100907003928.30019.qmail@sourceware.org \
    --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).