Re: Cannot compile jdk16 on latest -current

On Jan 15, 2008 3:02 PM, Jiawei Ye <leafy7382_at_gmail.com> wrote:

> On Jan 15, 2008 8:24 AM, Xin LI <delphij_at_delphij.net> wrote:
>
> > Jiawei Ye wrote:
> > > I have upgraded my machine to -current as of Jan 14. java/jdk16
> > stalled at
> > > va/jdk16/work/hotspot/src/share/vm/services
> > > -I/usr/ports/java/jdk16/work/hotspot/src/share/vm/utilities
> > > -I/usr/ports/java/jdk16/work/hotspot/src/cpu/i486/vm
> > > -I/usr/ports/java/jdk16/work/hotspot/src/os/bsd/vm
> > > -I/usr/ports/java/jdk16/work/hotspot/src/os_cpu/bsd_i486/vm
> > -I../generated
> > > -DHOTSPOT_BUILD_VERSION="\" 1.6.0_03-p3-leafy_15_jan_2008_05_57-b00\""
> > > -DHOTSPOT_BUILD_USER="\"root\"" -DHOTSPOT_RELEASE_VERSION="\"1.6.0\""
> > -O2
> > > -fno-strict-aliasing -pipe  -DCOMPILER2  -fno-rtti -fno-exceptions
> > -pthread
> > > -fcheck-new -m32 -march=i586 -pipe -DCOMPILER2 -fPIC -fno-rtti
> > > -fno-exceptions -pthread -fcheck-new -m32 -march=i586 -pipe -O3
> > > -fno-strict-aliasing -DVM_LITTLE_ENDIAN -Werror -Wpointer-arith
> > -Wconversion
> > > -Wsign-compare    -c -x c++-header -c
> > ../generated/incls/_precompiled.incl
> > > -o incls/_precompiled.incl.gch
> > > ^Cgmake[5]: *** Deleting file `incls/_precompiled.incl.gch'
> > > gmake[5]: *** [incls/_precompiled.incl.gch] Interrupt: 2
> > > gmake[4]: *** [the_vm] Interrupt: 2
> > > gmake[3]: *** [product] Interrupt: 2
> > > gmake[2]: *** [generic_build2] Interrupt: 2
> > > gmake[1]: *** [product] Interrupt: 2
> > > gmake: *** [hotspot-build] Interrupt: 2
> > >
> > > The compilation went on for 1.5hr before I killed it. Bootstrapped
> > with
> > > diablo-jdk15.
> > >
> > > Has anyone else seen this symptom?
> >
> > What does '^T' (Ctrl+T) say?
> >
> > Cheers,
> > - --
> > Xin LI <delphij_at_delphij.net>    http://www.delphij.net/
> >
>
> Here it is:
>
> load: 1.00  cmd: cc1plus 31106 [runnable] 4011.05u 0.46s 100% 109568k
> load: 1.00  cmd: cc1plus 31106 [runnable] 4011.73u 0.46s 100% 109568k
> load: 1.00  cmd: cc1plus 31106 [runnable] 4012.04u 0.46s 100% 109568k
> load: 1.00  cmd: cc1plus 31106 [runnable] 4012.31u 0.46s 100% 109568k
> load: 1.00  cmd: cc1plus 31106 [runnable] 4012.99u 0.46s 100% 109568k
> load: 1.00  cmd: cc1plus 31106 [runnable] 4013.31u 0.46s 100% 109568k
> load: 1.00  cmd: cc1plus 31106 [runnable] 4013.54u 0.46s 100% 109568k
> load: 1.00  cmd: cc1plus 31106 [runnable] 4015.31u 0.46s 100% 109568k
> load: 1.00  cmd: cc1plus 31106 [runnable] 4015.61u 0.46s 100% 109568k
> load: 1.00   cmd: cc1plus 31106 [runnable] 4015.83u 0.46s 100% 109568k
> load: 1.00  cmd: cc1plus 31106 [runnable] 4467.44u 0.46s 98% 109568k
> load: 1.02  cmd: cc1plus 31106 [runnable] 4586.39u 0.46s 98% 109568k
> load: 1.01  cmd: cc1plus 31106 [runnable] 4612.37u 0.46s 100% 109568k
>
> Regards,
>
>
> This compile has been going on for over 2hrs. The same system with an
older -current used to compile the whole JDK16 in about 2hrs, now the output
from ctrl-t

load: 1.00  cmd: cc1plus 31106 [runnable] 8489.21u 0.46s 100% 109568k

This certainly does not look right at all. Any suggestion to investigate
further?


Jiawei
-- 
"If it looks like a duck, walks like a duck, and quacks like a duck, then to
the end user it's a duck, and end users have made it pretty clear they want
a duck; whether the duck drinks hot chocolate or coffee is irrelevant."