From michi at complang.tuwien.ac.at Sun Nov 1 13:48:56 2009 From: michi at complang.tuwien.ac.at (Michael Starzinger) Date: Sun, 1 Nov 2009 13:48:56 +0100 Subject: [cacao] FYI: Cacao supports JMX Remote Monitoring and Management Message-ID: <7BD7D6FB-F35B-45B4-949D-DED279D924A2@complang.tuwien.ac.at> Hello! Since a few days Cacao successfully starts OpenJDKs JMX Monitoring and Management Agent if requested to do so. This allows you to remotely connect to Cacao with any JMX-compliant monitoring tool. If you want to know more about the topic you might want to check out JMX in general[1] or read my blog post[2] about this topic which also has a nice screenshot of how this might look like. References: [1] http://openjdk.java.net/groups/jmx/index.html [2] http://www.antforge.org/blog/2009/10/28/cacao-supports-jmx-remote-monitoring-and-management -michi From bugzilla-daemon at complang.tuwien.ac.at Tue Nov 10 16:59:16 2009 From: bugzilla-daemon at complang.tuwien.ac.at (bugzilla-daemon at complang.tuwien.ac.at) Date: Tue, 10 Nov 2009 16:59:16 +0100 Subject: [cacao] [Bug 135] New: cacao fails to build on arm with thumb2 Message-ID: http://server.complang.tuwien.ac.at/cgi-bin/bugzilla/show_bug.cgi?id=135 Summary: cacao fails to build on arm with thumb2 Product: CACAO Version: cacao-1.0.x branch Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: vm AssignedTo: cacao at complang.tuwien.ac.at ReportedBy: doko at ubuntu.com arm-linux-gnueabi-gcc -DHAVE_CONFIG_H -I. -I../../.. -I../../../src -I../../../src/vm/jit/arm -I../../../src/vm/jit/arm/linux -I../../../src "-I/build/buildd/openjdk-6-6b17~pre2/build/openjdk/jdk/src/solaris/javavm/export" "-I/build/buildd/openjdk-6-6b17~pre2/build/openjdk/jdk/src/share/javavm/export" "-I/build/buildd/openjdk-6-6b17~pre2/build/openjdk/jdk/src/solaris/hpi/export" "-I/build/buildd/openjdk-6-6b17~pre2/build/openjdk/jdk/src/share/hpi/export" -D__ARM__ -D__LINUX__ -std=c99 -pedantic -Wall -Wno-long-long -D_POSIX_C_SOURCE=200112L -D_XOPEN_SOURCE=600 -D_XOPEN_SOURCE_EXTENDED -D_BSD_SOURCE -D_REENTRANT -g -O2 -fno-strict-aliasing -MT sun_misc_Unsafe.lo -MD -MP -MF .deps/sun_misc_Unsafe.Tpo -c sun_misc_Unsafe.c -fPIC -DPIC -o .libs/sun_misc_Unsafe.o In file included from ../../../src/vm/stringlocal.h:34, from ../../../src/vmcore/class.h:46, from ../../../src/toolbox/logging.h:36, from ../../../src/vm/builtin.h:39, from ../../../src/vmcore/method.h:41, from ../../../src/mm/gc-common.h:35, from ../../../src/mm/memory.h:51, from sun_misc_Unsafe.c:33: ../../../src/vmcore/system.h: In function 'system_scandir': ../../../src/vmcore/system.h:381: warning: passing argument 4 of 'scandir' from incompatible pointer type /usr/include/dirent.h:252: note: expected 'int (*)(const struct dirent **, const struct dirent **)' but argument is of type 'int (*)(const void *, const void *)' /tmp/ccXIagkk.s: Assembler messages: /tmp/ccXIagkk.s:895: Error: selected processor does not support `swp ip,r1,[r2]' /tmp/ccXIagkk.s:897: Error: selected processor does not support `swpne r0,ip,[r2]' /tmp/ccXIagkk.s:949: Error: selected processor does not support `swp ip,r1,[r2]' /tmp/ccXIagkk.s:951: Error: selected processor does not support `swpne r0,ip,[r2]' make[6]: *** [sun_misc_Unsafe.lo] Error 1 make[6]: Leaving directory `/build/buildd/openjdk-6-6b17~pre2/build/cacao/cacao-0.99.4/src/native/vm' make[5]: *** [install-recursive] Error 1 "The ideal workaround is to use the __sync_val_compare_and_swap builtin in GCC (see the GCC info pages). This "does something that works", based on the build-time -march= flags and the running kernel." -- Configure bugmail: http://server.complang.tuwien.ac.at/cgi-bin/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From stefan at complang.tuwien.ac.at Tue Nov 17 13:19:26 2009 From: stefan at complang.tuwien.ac.at (Stefan Ring) Date: Tue, 17 Nov 2009 13:19:26 +0100 Subject: [cacao] JSR 133 & volatile Message-ID: <53e878390911170419g115f51fqdda2d8cfd8efbc9@mail.gmail.com> I?ve finally tidied up and committed my memory barrier-after-volatile-store patch which is required by the JSR 133 (Java Memory Model). It is x86_64 only. The tricky part is that for unresolved classes, the volatile-ness can not be known in advance, so the MFENCE is placed conservatively and patched out later. For this to work, it is carefully ensured that the 3-byte MFENCE is atomically overwritten by a 3-byte NOP and does not cross a (4-byte) word boundary. With this commit, the x86_64 version of CACAO should be JSR133-compliant, to the best of my knowledge. http://mips.complang.tuwien.ac.at/hg/cacao/rev/51bd70a3ff6f