public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/57208] Latest chromium compilation fails with enabled LTO
Date: Fri, 21 Jun 2013 13:01:00 -0000 [thread overview]
Message-ID: <bug-57208-4-Zp7WRGLMIV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57208-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57208
--- Comment #19 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
chrome.wpa.000i.cgraph:
_ZN3net12_GLOBAL__N_113DnsTCPAttempt12OnIOCompleteEi/8859591 (OnIOComplete)
@0x7f80e10be980
Type: function definition analyzed
Visibility: force_output prevailing_def_ironly
Address is taken.
References:
Referring: _ZN3net12_GLOBAL__N_113DnsTCPAttempt12DoSendLengthEi/8859587
(addr)_ZN3net12_GLOBAL__N_113DnsTCPAttempt11DoSendQueryEi/8859588
(addr)_ZN3net12_GLOBAL__N_113DnsTCPAttempt12DoReadLengthEi/8859589
(addr)_ZN3net12_GLOBAL__N_113DnsTCPAttempt14DoReadResponseEi/8859590
(addr)_ZN3net12_GLOBAL__N_113DnsTCPAttempt5StartERKN4base8CallbackIFviEEE/8859580
(addr)
Read from file: obj/net/dns/net.dns_transaction.o
Availability: available
Function flags:
Called by:
Calls: _ZN3net12_GLOBAL__N_113DnsTCPAttempt6DoLoopEi/8859585 (1.00 per call)
Has 1 outgoing edges for indirect calls.
marxin@marxinbox /ssd/chromium-2/src/out/Release $ grep
_ZN3net12_GLOBAL__N_113DnsTCPAttempt12OnIOCompleteEi *.s
chrome.ltrans16.s: leaq
_ZN3net12_GLOBAL__N_113DnsTCPAttempt12OnIOCompleteEi(%rip), %rax
chrome.ltrans29.s: leaq
_ZN3net12_GLOBAL__N_113DnsTCPAttempt12OnIOCompleteEi(%rip), %rsi
chrome.ltrans29.s: leaq
_ZN3net12_GLOBAL__N_113DnsTCPAttempt12OnIOCompleteEi(%rip), %rsi
chrome.ltrans29.s: .type
_ZN3net12_GLOBAL__N_113DnsTCPAttempt12OnIOCompleteEi, @function
chrome.ltrans29.s:_ZN3net12_GLOBAL__N_113DnsTCPAttempt12OnIOCompleteEi:
chrome.ltrans29.s: .size
_ZN3net12_GLOBAL__N_113DnsTCPAttempt12OnIOCompleteEi,
.-_ZN3net12_GLOBAL__N_113DnsTCPAttempt12OnIOCompleteEi
This actually looks like partitioning problem. I misread the dump ysterday - it
is a local function and it seems that somehow we manage to get referenc eto it
from ltrans16 while it is static to ltrans29. Can I see .cgraph dump of
ltrans16? If you have -fdump-tree-all dumps (or you can just rebuild ltrans16
with this dump) it should be possible to grep the dumps to work out if the
symbol appears as a result of some constant folding.
next prev parent reply other threads:[~2013-06-21 13:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 12:30 [Bug c++/57208] New: Latest chromium compilation fails with enabled LTO [4.8.1/4.9.0] marxin.liska at gmail dot com
2013-05-08 12:32 ` [Bug c++/57208] " marxin.liska at gmail dot com
2013-06-03 14:50 ` [Bug c++/57208] Latest chromium compilation fails with enabled LTO marxin.liska at gmail dot com
2013-06-03 15:17 ` marxin.liska at gmail dot com
2013-06-05 12:12 ` izamyatin at gmail dot com
2013-06-05 16:26 ` marxin.liska at gmail dot com
2013-06-17 21:46 ` marxin.liska at gmail dot com
2013-06-19 17:03 ` hubicka at gcc dot gnu.org
2013-06-19 17:51 ` ian at airs dot com
2013-06-19 18:04 ` ian at airs dot com
2013-06-19 18:24 ` hubicka at gcc dot gnu.org
2013-06-19 18:27 ` jakub at gcc dot gnu.org
2013-06-19 23:14 ` hubicka at gcc dot gnu.org
2013-06-20 6:26 ` jakub at gcc dot gnu.org
2013-06-20 20:31 ` marxin.liska at gmail dot com
2013-06-21 12:55 ` hubicka at gcc dot gnu.org
2013-06-21 13:01 ` hubicka at gcc dot gnu.org [this message]
2013-06-21 13:07 ` marxin.liska at gmail dot com
2013-06-22 21:19 ` marxin.liska at gmail dot com
2013-06-22 21:43 ` hubicka at gcc dot gnu.org
2013-06-22 22:05 ` hubicka at ucw dot cz
2013-06-23 12:20 ` hubicka at ucw dot cz
2013-06-24 10:24 ` jamborm at gcc dot gnu.org
2013-06-24 16:10 ` jamborm at gcc dot gnu.org
2013-06-24 22:25 ` marxin.liska at gmail dot com
2013-06-25 11:02 ` jamborm at gcc dot gnu.org
2013-07-02 16:42 ` jamborm at gcc dot gnu.org
2013-07-02 16:43 ` jamborm at gcc dot gnu.org
2013-07-17 14:14 ` marxin.liska at gmail dot com
2022-01-01 22:58 ` pinskia 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-57208-4-Zp7WRGLMIV@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).