public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/55683] [4.8 Regression] ICE in inline_call, at ipa-inline-transform.c:270 Date: Fri, 14 Dec 2012 10:26:00 -0000 [thread overview] Message-ID: <bug-55683-4-W3QZ83btqk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55683-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55683 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> 2012-12-14 10:25:53 UTC --- 263 #ifdef ENABLE_CHECKING 264 /* Verify that estimated growth match real growth. Allow off-by-one 265 error due to INLINE_SIZE_SCALE roudoff errors. */ 266 gcc_assert (!update_overall_summary || !overall_size 267 || abs (estimated_growth - (new_size - old_size)) <= 1 268 /* FIXME: a hack. Edges with false predicate are accounted 269 wrong, we should remove them from callgraph. */ 270 || predicated); (gdb) p update_overall_summary $1 = true (gdb) p overall_size $2 = (int *) 0x1bb83a0 <_ZL12overall_size> (gdb) p estimated_growth - (new_size - old_size) $3 = -2 (gdb) p predicated $4 = false (gdb) p new_size $5 = 32 (gdb) p old_size $6 = 22 (gdb) p estimated_growth $7 = 8 So this is an off-by-two error. Do multiple INLINE_SIZE_SCALE roundoff errors not accumulate?
next prev parent reply other threads:[~2012-12-14 10:26 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-12-14 8:56 [Bug tree-optimization/55683] New: " rguenth at gcc dot gnu.org 2012-12-14 8:57 ` [Bug tree-optimization/55683] " rguenth at gcc dot gnu.org 2012-12-14 8:59 ` rguenth at gcc dot gnu.org 2012-12-14 9:57 ` jakub at gcc dot gnu.org 2012-12-14 10:26 ` rguenth at gcc dot gnu.org [this message] 2012-12-14 10:31 ` jakub at gcc dot gnu.org 2012-12-14 10:43 ` rguenth at gcc dot gnu.org 2012-12-14 12:14 ` jamborm at gcc dot gnu.org 2012-12-16 11:58 ` rguenth at gcc dot gnu.org 2012-12-18 12:47 ` rguenth at gcc dot gnu.org 2012-12-18 13:40 ` hubicka at ucw dot cz 2012-12-18 16:40 ` hubicka at gcc dot gnu.org 2012-12-18 17:16 ` hubicka at gcc dot gnu.org 2012-12-19 11:42 ` hubicka at gcc dot gnu.org 2012-12-19 11:47 ` hubicka at gcc dot gnu.org 2012-12-19 15:28 ` rguenth at gcc dot gnu.org 2013-01-10 16:59 ` jamborm 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-55683-4-W3QZ83btqk@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).