Tom Tromey wrote:
"Ian" == Ian Lance Taylor <[EMAIL PROTECTED]> writes:
Ian> But note that IPA via LTO is not going to permit callbacks into the
Ian> front end, because there isn't going to be a front end. So the
Ian> information needs to be represented in GIMPLE somewhere.
Unfortunately ther
On Wed, Oct 11, 2006 at 11:12:52AM -0600, Tom Tromey wrote:
> > "Ian" == Ian Lance Taylor <[EMAIL PROTECTED]> writes:
>
> Ian> But note that IPA via LTO is not going to permit callbacks into the
> Ian> front end, because there isn't going to be a front end. So the
> Ian> information needs to
Andrew> Anyway, a front end callback is surely good enought for a proof of
Andrew> concept.
OBJ_TYPE_REF exists, is GIMPLE, and we already have a patch to add it
to gcj.
Tom
> "Ian" == Ian Lance Taylor <[EMAIL PROTECTED]> writes:
Ian> But note that IPA via LTO is not going to permit callbacks into the
Ian> front end, because there isn't going to be a front end. So the
Ian> information needs to be represented in GIMPLE somewhere.
Unfortunately there are lots of u
Ian Lance Taylor writes:
> Andrew Haley <[EMAIL PROTECTED]> writes:
>
> > Yes. You'll need to represent virtual function calls at the GIMPLE
> > level, or to keep track of which calls are associated with which
> > methods. This is key to getting IPA to work.
> >
> > It should be fairly e
Andrew Haley <[EMAIL PROTECTED]> writes:
> Yes. You'll need to represent virtual function calls at the GIMPLE
> level, or to keep track of which calls are associated with which
> methods. This is key to getting IPA to work.
>
> It should be fairly easy, given a class and a vtable offset, to fin
> "Paul" == Paul Biggar <[EMAIL PROTECTED]> writes:
Paul> I've come to a bit of an impasse in the (java) escape analysis. In
Paul> order to do interprocedural analysis effectively, I need to know what
Paul> methods are called.
Paul> So its all vtables, function lookups and indirect function c
Paul Biggar writes:
> I've come to a bit of an impasse in the (java) escape analysis. In
> order to do interprocedural analysis effectively, I need to know what
> methods are called. However, it is rarely the case that this
> information is available. For example, a call to System.out.println
