public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/55792] [4.8 Regression] Bad memory access with profiledbootstrap and LTO Date: Wed, 09 Jan 2013 17:13:00 -0000 [thread overview] Message-ID: <bug-55792-4-DKtdLSeeUK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55792-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55792 --- Comment #20 from H.J. Lu <hjl.tools at gmail dot com> 2013-01-09 17:12:45 UTC --- we put the remapped block in line_table: #0 0x000000000101d8cf in get_combined_adhoc_loc (set=0x7ffff7ffc000, locus=968541695, data=0x7fffe8d6fe60) at /export/gnu/import/git/gcc/libcpp/line-map.c:146 #1 0x00000000009f839d in gimple_set_block (g=0x7fffe8d759b0, block=0x7fffe8d6fe60) at /export/gnu/import/git/gcc/gcc/gimple.h:1226 #2 0x0000000000a016fd in remap_gimple_stmt (stmt=0x7fffe910e0a0, id=0x7fffffffd900) at /export/gnu/import/git/gcc/gcc/tree-inline.c:1473 #3 0x0000000000a01a04 in copy_bb (id=0x7fffffffd900, bb=0x7fffe910c888, frequency_scale=1000000, count_scale=1779) at /export/gnu/import/git/gcc/gcc/tree-inline.c:1539 #4 0x0000000000a03f56 in copy_cfg_body (id=0x7fffffffd900, count=48912247, frequency_scale=1000000, entry_block_map=0x7ffff138aaf8, exit_block_map=0x7fffe8d58270, blocks_to_copy=0x0, new_entry=0x0) at /export/gnu/import/git/gcc/gcc/tree-inline.c:2259 #5 0x0000000000a047fa in copy_body (id=0x7fffffffd900, count=48912247, frequency_scale=1000000, entry_block_map=0x7ffff138aaf8, exit_block_map=0x7fffe8d58270, blocks_to_copy=0x0, new_entry=0x0) at /export/gnu/import/git/gcc/gcc/tree-inline.c:2457 #6 0x0000000000a0881e in expand_call_inline (bb=0x7ffff138aaf8, stmt=0x7ffff1390980, id=0x7fffffffd900) at /export/gnu/import/git/gcc/gcc/tree-inline.c:4041 #7 0x0000000000a08c6f in gimple_expand_calls_inline (bb=0x7ffff138aaf8, id=0x7fffffffd900) at /export/gnu/import/git/gcc/gcc/tree-inline.c:4147 But tree node in line_table is ignored by GC.
next prev parent reply other threads:[~2013-01-09 17:13 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-12-22 18:05 [Bug bootstrap/55792] New: " hjl.tools at gmail dot com 2012-12-22 18:43 ` [Bug bootstrap/55792] " hjl.tools at gmail dot com 2012-12-22 20:13 ` hjl.tools at gmail dot com 2013-01-03 19:03 ` hjl.tools at gmail dot com 2013-01-04 23:58 ` hjl.tools at gmail dot com 2013-01-05 16:47 ` hjl.tools at gmail dot com 2013-01-05 17:21 ` hjl.tools at gmail dot com 2013-01-07 10:13 ` rguenth at gcc dot gnu.org 2013-01-07 15:41 ` hjl.tools at gmail dot com 2013-01-07 16:02 ` rguenth at gcc dot gnu.org 2013-01-07 16:03 ` [Bug bootstrap/55792] [4.8 Regression] " rguenth at gcc dot gnu.org 2013-01-07 17:55 ` dnovillo at gcc dot gnu.org 2013-01-07 22:14 ` hjl.tools at gmail dot com 2013-01-07 23:30 ` hjl.tools at gmail dot com 2013-01-08 1:20 ` hjl.tools at gmail dot com 2013-01-08 10:17 ` rguenth at gcc dot gnu.org 2013-01-08 17:13 ` hjl.tools at gmail dot com 2013-01-09 0:23 ` hjl.tools at gmail dot com 2013-01-09 9:32 ` rguenth at gcc dot gnu.org 2013-01-09 16:11 ` hjl.tools at gmail dot com 2013-01-09 17:13 ` hjl.tools at gmail dot com [this message] 2013-01-09 18:22 ` rguenth at gcc dot gnu.org 2013-01-09 18:38 ` hjl.tools at gmail dot com 2013-01-09 22:52 ` hjl.tools at gmail dot com 2013-01-10 11:30 ` rguenth at gcc dot gnu.org 2013-01-10 12:16 ` rguenth at gcc dot gnu.org 2013-01-10 13:43 ` rguenth at gcc dot gnu.org 2013-01-10 14:08 ` rguenth at gcc dot gnu.org 2013-01-10 14:12 ` rguenth at gcc dot gnu.org 2013-01-10 15:29 ` rguenth at gcc dot gnu.org 2013-01-10 15:35 ` rguenth at gcc dot gnu.org 2013-01-10 17:03 ` hjl.tools at gmail dot com 2013-01-10 19:36 ` hjl.tools at gmail dot com 2013-01-11 17:37 ` hubicka at ucw dot cz 2013-01-14 13:43 ` rguenth at gcc dot gnu.org 2013-01-14 13:50 ` rguenth at gcc dot gnu.org 2013-01-14 13:51 ` rguenth at gcc dot gnu.org 2013-01-15 14:32 ` 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=bug-55792-4-DKtdLSeeUK@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).