This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Serialization bug fixes


Tom Tromey writes:
 > >>>>> "Andrew" == Andrew Haley <aph@redhat.com> writes:
 > 
 > Andrew> For Tom Tromey: any method that needs to find its caller needs to be
 > Andrew> compiled without sibcalls,so we need some common infrastructure for
 > Andrew> this.
 > 
 > It seems to me that basically all user programs must be compiled
 > without sibcalls.

I was just about ready to come to that conclusion.

 > Maybe we'd like to compile parts of libgcj itself with sibcalls
 > enabled, though figuring out which parts are safe and would benefit
 > might be tricky.

It's not so hard, really: anything that needs to walk the stack to
find its caller must not be called via a sibcall.

 > I would suggest that we simply disable sibcalls in the front end and
 > let the user explicitly enable them with a command-line option, but
 > from the manual it looks like some -O options enable sibcalls.

I guess we just turn sibcalls off lin libgcj.spec.

Andrew.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]