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 22:52:00 -0000 [thread overview]
Message-ID: <bug-55792-4-K6uJw3UxPZ@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 #23 from H.J. Lu <hjl.tools at gmail dot com> 2013-01-09 22:51:36 UTC ---
The old BLOCK came from
(gdb) bt
#0 remap_block (block=0x7fffffffd690, id=0x7fffffffd840) at
/export/gnu/import/git/gcc/gcc/tree-inline.c:624
#1 0x00000000009fe52a in remap_blocks (block=0x7ffff1393d20,
id=0x7fffffffd840)
at /export/gnu/import/git/gcc/gcc/tree-inline.c:645
#2 0x00000000009fe586 in remap_blocks (block=0x7ffff1385370,
id=0x7fffffffd840)
at /export/gnu/import/git/gcc/gcc/tree-inline.c:648
#3 0x00000000009fe586 in remap_blocks (block=0x7ffff1385320,
id=0x7fffffffd840)
at /export/gnu/import/git/gcc/gcc/tree-inline.c:648
---Type <return> to continue, or q <return> to quit---
#4 0x00000000009fe586 in remap_blocks (block=0x7ffff1385280,
id=0x7fffffffd840)
at /export/gnu/import/git/gcc/gcc/tree-inline.c:648
#5 0x00000000009fe586 in remap_blocks (block=0x7ffff13851e0,
id=0x7fffffffd840)
at /export/gnu/import/git/gcc/gcc/tree-inline.c:648
#6 0x0000000000a0bc63 in tree_function_versioning (old_decl=0x7fffec94b400,
new_decl=0x7fffe9105000, tree_map=0x0,
update_clones=true, args_to_skip=0x0, skip_return=false,
blocks_to_copy=0x0, new_entry=0x0)
at /export/gnu/import/git/gcc/gcc/tree-inline.c:5225
---Type <return> to continue, or q <return> to quit---
#7 0x00000000007d2d05 in save_inline_function_body (node=0x7ffff1753818)
at /export/gnu/import/git/gcc/gcc/ipa-inline-transform.c:354
#8 0x00000000007d2ec6 in inline_transform (node=0x7ffff1753818) at
/export/gnu/import/git/gcc/gcc/ipa-inline-transform.c:411
#9 0x00000000008adbe3 in execute_one_ipa_transform_pass (node=0x7ffff1753818,
ipa_pass=0x16cfc80 <pass_ipa_inline>)
at /export/gnu/import/git/gcc/gcc/passes.c:2177
#10 0x00000000008add31 in execute_all_ipa_transforms () at
/export/gnu/import/git/gcc/gcc/passes.c:2213
#11 0x00000000005da348 in expand_function (node=0x7ffff1753818) at
/export/gnu/import/git/gcc/gcc/cgraphunit.c:1634
---Type <return> to continue, or q <return> to quit---
#12 0x00000000005da821 in expand_all_functions () at
/export/gnu/import/git/gcc/gcc/cgraphunit.c:1745
#13 0x00000000005db2ab in compile () at
/export/gnu/import/git/gcc/gcc/cgraphunit.c:2043
#14 0x000000000053c60a in lto_main () at
/export/gnu/import/git/gcc/gcc/lto/lto.c:3390
#15 0x0000000000999401 in compile_file () at
/export/gnu/import/git/gcc/gcc/toplev.c:545
#16 0x000000000099b3e4 in do_compile () at
/export/gnu/import/git/gcc/gcc/toplev.c:1878
#17 0x000000000099b54f in toplev_main (argc=28, argv=0x7fffffffdc78) at
/export/gnu/import/git/gcc/gcc/toplev.c:1954
#18 0x0000000000fff958 in main (argc=28, argv=0x7fffffffdc78) at
/export/gnu/import/git/gcc/gcc/main.c:36
(gdb) p id->block
$90 = (tree) 0x0
next prev parent reply other threads:[~2013-01-09 22:52 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
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 [this message]
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-K6uJw3UxPZ@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).