This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: basic block reordering + java
- To: Andrew Haley <aph at cambridge dot redhat dot com>
- Subject: Re: basic block reordering + java
- From: Jakub Jelinek <jakub at redhat dot com>
- Date: Fri, 21 Sep 2001 16:37:58 +0200
- Cc: Anthony Green <green at redhat dot com>, "Gcc at Gcc dot Gnu. Org" <gcc at gcc dot gnu dot org>, "Java at Gcc dot Gnu. Org" <java at gcc dot gnu dot org>
- References: <005601c142aa$039ed920$5be6b4cd@cygnus.com> <15275.20209.228138.771073@cuddles.cambridge.redhat.com>
- Reply-To: Jakub Jelinek <jakub at redhat dot com>
On Fri, Sep 21, 2001 at 03:30:09PM +0100, Andrew Haley wrote:
> Anthony Green writes:
> >
> > Also, I find that if the last NullPointerException branch is taken,
> > printStackTrace() will produce incorrect results. You end up seeing the
> > function after this in place of the one calling _Jv_ThrowNullPointerException.
> > Should we be backing up the program counter somewhere? (or emitting a NOP at
> > the very end of each function?)
>
> We use backtrace() from glibc. If it's wrong, this is a glibc bug.
Note that with tail call optimization some routines can be skipped in the
backtrace. I don't know if this is the case here, but I thought I'd mention
this...
Jakub