Changeset: 8d492f1dfd1b
Author:cl
Date: 2013-07-18 03:37 -0700
URL: http://hg.openjdk.java.net/jdk8/build/corba/rev/8d492f1dfd1b
Added tag jdk8-b99 for changeset 3f67804ab613
! .hgtags
Changeset: bb416ee2a79b
Author:cl
Date: 2013-07-18 03:38 -0700
URL: http://hg.openjdk.java.net/jdk8/build/hotspot/rev/bb416ee2a79b
Added tag jdk8-b99 for changeset 81b6cb70717c
! .hgtags
Changeset: 4fd722afae5c
Author:cl
Date: 2013-07-18 03:38 -0700
URL: http://hg.openjdk.java.net/jdk8/build/jaxws/rev/4fd722afae5c
Added tag jdk8-b99 for changeset 8ef83d4b23c9
! .hgtags
Changeset: 043da456d316
Author:cl
Date: 2013-07-18 03:38 -0700
URL: http://hg.openjdk.java.net/jdk8/build/jaxp/rev/043da456d316
Added tag jdk8-b99 for changeset adf49c3ef83c
! .hgtags
Changeset: 3b071f506ab9
Author:joehw
Date: 2013-07-09 16:34 -0700
URL:
Changeset: d2dcb110e9db
Author:cl
Date: 2013-07-18 03:37 -0700
URL: http://hg.openjdk.java.net/jdk8/build/rev/d2dcb110e9db
Added tag jdk8-b99 for changeset 59dc9da81379
! .hgtags
Changeset: e73f00139fb5
Author:cl
Date: 2013-07-18 03:39 -0700
URL: http://hg.openjdk.java.net/jdk8/build/langtools/rev/e73f00139fb5
Added tag jdk8-b99 for changeset 6d85acab769e
! .hgtags
Changeset: d6158f8d7235
Author:vromero
Date: 2013-07-04 10:35 +0100
URL:
Changeset: 10503ced6cc2
Author:cl
Date: 2013-07-18 03:39 -0700
URL: http://hg.openjdk.java.net/jdk8/build/nashorn/rev/10503ced6cc2
Added tag jdk8-b99 for changeset 10a1ab9e20a4
! .hgtags
Changeset: 313bdcd2fd22
Author:sundar
Date: 2013-07-03 00:08 +0530
URL:
Hello everyone-
This is a small set of changes to switch from gcc to clang when building
on MacOS, and also enable building on MacOS 8.x
Here is the bug report:
http://bugs.sun.com/view_bug.do?bug_id=8019470
Here are the webrevs:
Hotspot only:
Just to satisfy my curiosity: what are advantages of using clang instead of
gcc?
On Jul 24, 2013, at 2:15 AM, Tim Bell tim.b...@oracle.com wrote:
Hello everyone-
This is a small set of changes to switch from gcc to clang when building on
MacOS, and also enable building on MacOS 8.x
Nice work!
toolchain.m4::
- Wouldn't COMPILER_NAME=clang now be dependent upon which compiler is used?
- It also seems to require that gcc still be present for the containing
conditional; 509 if test x$GCC = xyes; then
Mike
On Jul 23 2013, at 15:15 , Tim Bell wrote:
Hello everyone-
Changeset: bd1dc81da579
Author:amurillo
Date: 2013-07-12 17:08 -0700
URL: http://hg.openjdk.java.net/jdk8/build/hotspot/rev/bd1dc81da579
8020382: new hotspot build - hs25-b42
Reviewed-by: jcoomes
! make/hotspot_version
Changeset: f4311079200c
Author:brutisso
Date:
Hello Leonid:
Just to satisfy my curiosity: what are advantages of using clang instead of gcc?
I am a mere messenger here, but I am told that clang/clang++:
- is command line compatible with gcc
- is faster
- produces better diagnostic messages
- clang on MacOS is under active development
In toolchain.m4
267 elif test x$OPENJDK_TARGET_OS = xmacosx; then
268 COMPILER_CHECK_LIST=clang gcc cc
Aren't clang cc the same? (/usr/bin/cc - clang)
Or are there instances of macosx that do not have the symlink?
That's the only question I could find. Pretty simple change.
Hi great all,
I found this article:
http://www.phoronix.com/scan.php?page=articleitem=llvm_clang33_3waynum=2
http://www.phoronix.com/scan.php?page=articleitem=llvm_clang33_3waynum=3
http://www.phoronix.com/scan.php?page=articleitem=llvm_clang33_3waynum=4
And GCC wins all on performance issues.
14 matches
Mail list logo