public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/50394] [meta-bug] Issues with building libreoffice with LTO
Date: Wed, 21 Sep 2011 13:11:00 -0000	[thread overview]
Message-ID: <bug-50394-4-9os5baQmwB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50394-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50394

--- Comment #21 from Jan Hubicka <hubicka at ucw dot cz> 2011-09-21 13:08:43 UTC ---
> is altogether more hairy - we create at run-time C++ vtables packed with
> trampolines so we can intercept / model native C++ objects and interact with
> them via python etc. that would need some more intense debugging love I guess.

Hmm, this sounds scary. (I remember Kendy explaining me this years back when
OOo
was ported to x86_64.) More or less everything that is reachable externally
ought to
be annotated with used/externally_visible attributes or the assembly wrappers
has
to be visible at linktime.  Is there some short overview of the machinery?
(or could you explain it somehow? :)

Honza


  parent reply	other threads:[~2011-09-21 13:10 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-14  9:56 [Bug lto/50394] New: " hubicka at gcc dot gnu.org
2011-09-14 10:09 ` [Bug lto/50394] " hubicka at gcc dot gnu.org
2011-09-14 16:08 ` markus at trippelsdorf dot de
2011-09-15 15:47 ` hubicka at gcc dot gnu.org
2011-09-15 16:56 ` markus at trippelsdorf dot de
2011-09-16  9:44 ` hubicka at gcc dot gnu.org
2011-09-16 10:11 ` hubicka at gcc dot gnu.org
2011-09-16 10:14 ` hubicka at gcc dot gnu.org
2011-09-16 10:20 ` hubicka at gcc dot gnu.org
2011-09-16 10:25 ` hubicka at gcc dot gnu.org
2011-09-16 11:36 ` hubicka at gcc dot gnu.org
2011-09-16 15:18 ` hubicka at gcc dot gnu.org
2011-09-17 19:52 ` markus at trippelsdorf dot de
2011-09-17 22:24 ` markus at trippelsdorf dot de
2011-09-18 23:55 ` hubicka at ucw dot cz
2011-09-19 17:09 ` hubicka at gcc dot gnu.org
2011-09-20 16:58 ` markus at trippelsdorf dot de
2011-09-20 22:54 ` hubicka at ucw dot cz
2011-09-21  8:10 ` markus at trippelsdorf dot de
2011-09-21  9:57 ` hubicka at ucw dot cz
2011-09-21 12:10 ` michael.meeks at suse dot com
2011-09-21 13:11 ` hubicka at ucw dot cz [this message]
2011-09-22 20:31 ` markus at trippelsdorf dot de
2011-09-22 20:41   ` Jan Hubicka
2011-09-22 20:48 ` hubicka at ucw dot cz
2011-09-23  9:30 ` michael.meeks at suse dot com
2011-09-23 12:45 ` markus at trippelsdorf dot de
2011-09-23 16:01 ` markus at trippelsdorf dot de
2011-10-06 20:52 ` hubicka at gcc dot gnu.org
2014-04-20 17:44 ` nheghathivhistha at gmail dot com
2014-04-20 17:58 ` hubicka at gcc dot gnu.org
2015-05-04 14:12 ` steffen at hauihau dot de
2015-05-12 10:39 ` steffen at hauihau dot de

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-50394-4-9os5baQmwB@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).