public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/50568] [4.7 Regression] Massive LTO failures Date: Fri, 30 Sep 2011 15:57:00 -0000 [thread overview] Message-ID: <bug-50568-4-6V85Bm6jCX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50568-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50568 --- Comment #32 from hjl at gcc dot gnu.org <hjl at gcc dot gnu.org> 2011-09-30 15:48:56 UTC --- Author: hjl Date: Fri Sep 30 15:48:51 2011 New Revision: 179395 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=179395 Log: Use 64bit integer for LTO symbol ID. gcc/lto 2011-09-30 H.J. Lu <hongjiu.lu@intel.com> Andi Kleen <ak@linux.intel.com> PR lto/50568 * lto.c (lto_splay_tree_delete_id): New. (lto_splay_tree_compare_ids): Likewise. (lto_splay_tree_lookup): Likewise. (lto_splay_tree_id_equal_p): Likewise. (lto_splay_tree_insert): Likewise. (lto_splay_tree_new): Likewise. (lto_resolution_read): Change id to unsigned HOST_WIDE_INT. Use lto_splay_tree_id_equal_p and lto_splay_tree_lookup. (create_subid_section_table): Use lto_splay_tree_lookup and lto_splay_tree_insert. (lto_file_read): Use lto_splay_tree_new. lto-plugin/ 2011-09-30 H.J. Lu <hongjiu.lu@intel.com> Andi Kleen <ak@linux.intel.com> PR lto/50568 * lto-plugin.c (sym_aux): Change id to unsigned long long. (plugin_symtab): Likewise. (dump_symtab): Likewise. (resolve_conflicts): Likewise. (process_symtab): Likewise. Modified: trunk/gcc/lto/ChangeLog trunk/gcc/lto/lto.c trunk/lto-plugin/ChangeLog trunk/lto-plugin/lto-plugin.c
next prev parent reply other threads:[~2011-09-30 15:49 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-29 15:50 [Bug lto/50568] New: " hjl.tools at gmail dot com 2011-09-29 15:55 ` [Bug lto/50568] " hjl.tools at gmail dot com 2011-09-29 16:02 ` andi-gcc at firstfloor dot org 2011-09-29 16:04 ` hjl.tools at gmail dot com 2011-09-29 16:18 ` hjl.tools at gmail dot com 2011-09-29 18:12 ` hjl.tools at gmail dot com 2011-09-29 18:16 ` andi-gcc at firstfloor dot org 2011-09-29 18:18 ` hjl.tools at gmail dot com 2011-09-29 18:19 ` hjl.tools at gmail dot com 2011-09-29 18:20 ` andi-gcc at firstfloor dot org 2011-09-29 18:21 ` andi-gcc at firstfloor dot org 2011-09-29 18:26 ` hjl.tools at gmail dot com 2011-09-29 18:28 ` hjl.tools at gmail dot com 2011-09-29 18:29 ` hjl.tools at gmail dot com 2011-09-29 18:29 ` andi-gcc at firstfloor dot org 2011-09-29 18:35 ` andi-gcc at firstfloor dot org 2011-09-29 18:45 ` hjl.tools at gmail dot com 2011-09-29 18:45 ` hjl.tools at gmail dot com 2011-09-29 20:47 ` andi-gcc at firstfloor dot org 2011-09-29 20:55 ` hjl.tools at gmail dot com 2011-09-29 22:23 ` hjl.tools at gmail dot com 2011-09-29 22:23 ` hjl.tools at gmail dot com 2011-09-29 22:28 ` hjl.tools at gmail dot com 2011-09-29 22:53 ` hjl.tools at gmail dot com 2011-09-29 23:17 ` andi-gcc at firstfloor dot org 2011-09-29 23:21 ` hjl.tools at gmail dot com 2011-09-29 23:22 ` hjl.tools at gmail dot com 2011-09-29 23:32 ` andi-gcc at firstfloor dot org 2011-09-29 23:34 ` andi-gcc at firstfloor dot org 2011-09-30 0:33 ` hjl.tools at gmail dot com 2011-09-30 0:45 ` andi-gcc at firstfloor dot org 2011-09-30 6:00 ` hjl.tools at gmail dot com 2011-09-30 15:57 ` hjl at gcc dot gnu.org [this message] 2011-10-10 15:14 ` rguenth at gcc dot gnu.org 2021-08-24 13:10 ` hjl.tools at gmail dot com
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-50568-4-6V85Bm6jCX@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).