Re: [OpenJDK Rasterizer] AWT & gcc 4.8 optimization options

2016-01-15 Thread Jim Graham
The lookups were written in 1997-ish when processors had different vectorization/computation tradeoffs. It might be interesting to investigate a non-table version of the macros and see how the performance differs... ...jim On 1/15/16 1:49 PM, Sergey Bylokhov wrote: H

Re: [OpenJDK Rasterizer] AWT & gcc 4.8 optimization options

2016-01-15 Thread Sergey Bylokhov
Hi, I found that in case of vectorisation on of the main hotspot is out table lookup pattern: mul8table/div8table which cannot be vectorized. Another hotspot is a many conditions inside the main loops. On 15/01/16 20:14, Laurent Bourgès wrote: Sergey, Did you made any progress ? I finally

Re: [OpenJDK Rasterizer] AWT & gcc 4.8 optimization options

2016-01-15 Thread Laurent Bourgès
Sergey, Did you made any progress ? I finally looked at the preprocessed C code and also enabled ftree-vectorizer-verbose output: CFLAGS := -save-temps -ftree-vectorize -ftree-vectorizer-verbose=2 $(CFLAGS_JDKLIB) $(LIBAWT_CFLAGS), \ I looked at the IntArgbPreSrcMaskFill hotspot (in my Elli