This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
RE: IA64 status
- To: "'Richard Henderson'" <rth at redhat dot com>, "Boehm, Hans" <hans_boehm at hp dot com>
- Subject: RE: IA64 status
- From: "Boehm, Hans" <hans_boehm at hp dot com>
- Date: Tue, 11 Sep 2001 17:13:40 -0700
- Cc: "'java at gcc dot gnu dot org'" <java at gcc dot gnu dot org>
Here's a self-contained example that parallels the one I was using, but is
legal to post. In this case I believe the load instruction causing problems
is numbered 46:
Bug.java:
---------------------
public
class Bug
{
private float x;
private float y;
public static float
f()
{
return 1.0f;
}
public synchronized void
g()
{
x = f( );
y = 10000.00f;
}
}
-------------------
> -----Original Message-----
> From: Richard Henderson [mailto:rth@redhat.com]
> Sent: Tuesday, September 11, 2001 4:44 PM
> To: Boehm, Hans
> Cc: 'java@gcc.gnu.org'
> Subject: Re: IA64 status
>
>
> On Tue, Sep 11, 2001 at 04:39:08PM -0700, Boehm, Hans wrote:
> > As far as I can tell, what's happening is the following:
> >
> > 1) An rtl load instruction is generated to load a floating
> point constant.
> > It is viewed as being able to trap. The specific
> instruction in this case
> > is:
> >
> > (insn 72 70 118 (set (reg:SF 360)
> > (mem/u/f:SF (reg/f:DI 361) 0)) -1 (nil)
> > (expr_list:REG_DEAD (reg/f:DI 361)
> > (expr_list:REG_EH_REGION (const_int 1 [0x1])
>
> What's the test case for this?
>
>
> r~
>