OpenJDK7 and the JavaOne preview (M3) release
mark at klomp.org
Sun May 24 15:48:04 PDT 2009
On Sat, 2009-05-23 at 09:18 +0200, Mark Wielaard wrote:
> On Fri, 2009-05-22 at 20:05 +0200, Mark Wielaard wrote:
> > On Fri, 2009-05-22 at 18:35 +0100, Andrew John Hughes wrote:
> > > Are there any negative side-effects to having this code applied all the time?
> > No, the patches are designed so that without the property set the old
> > pipeline is used.
> That said, if you do build with --disable-xrender then the font issue
> doesn't occur. So something else is broken with the xrender support :(
> I propose that we disable xrender support by default for now while we
> figure out what else is borked.
Found it. The X11 pipeline initialization is a bit tricky to follow. The
xrender patches tried to clear that up at one point by making the
initialization of the X11SurfaceData explicit (just like the
XRSurfaceData). Although that code is nicer and cleaner, the new font
code depends on the implicit static initializer calling order. That is a
bit yucky, but lets play along and make sure that no explicit
initialization is done:
2009-05-24 Mark Wielaard <mark at klomp.org>
* patches/xrender/icedtea-001.patch: Initialize X11SurfaceData
implicitly, not explicitly.
Now both the standard X11 pipeline (default) and the XRender pipeline
(-Dsun.java2d.xrender=True) work again against IcedTea7.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3940 bytes
Desc: not available
Url : http://mail.openjdk.java.net/pipermail/xrender-dev/attachments/20090525/daab2d5f/attachment.bin
More information about the xrender-dev