Hello,
I was waiting for Magnus to look at this since he is more involved in
this code at the moment. I think it looks good ok, but would prefer if
he got the chance to look at it too.
/Erik
On 2014-03-06 01:11, Henry Jen wrote:
Ping! Is three any concern on this patch? I got JPRT reports
Looks good to me. Just one question, since clang otherwise duplicates the gcc
flags: is it correct to drop -fPIC in clang?
/Magnus
On 6 mar 2014, at 09:36, Erik Joelsson erik.joels...@oracle.com wrote:
Hello,
I was waiting for Magnus to look at this since he is more involved in this
I cannot find doc regarding to -fPIC in clang, thus I leave it empty
after googled a little bit.
There is a code generation option for lli, -relocation-model=pic, which
seems to be default for clang[1].
[1] http://clang.llvm.org/doxygen/CodeGenOptions_8h_source.html
Cheers,
Henry
On
Ping! Is three any concern on this patch? I got JPRT reports no problem
and other reports success.
I hope we can get this in as early as we can because build is evloving
quickly, and I think it only can get better after pushed for more tests.
Cheers,
Henry
On 02/26/2014 12:23 AM, Henry Jen
Hi,
Please review a webrev to enable XCode5 build on Mac OS X, this webrev
add basic clang flags and detect Xcode version to set default toolchain
to clang for Xcode5 and after, otherwise set to gcc for Mac OS X.
http://cr.openjdk.java.net/~henryjen/jdk9/8019470/1/webrev/
This patch build
On 07/24/13 09:44 PM, David Holmes wrote:
On 25/07/2013 8:48 AM, Tim Bell wrote:
Christian:
That's not true. I've added Mac OS X support with the same change.
For building hotspot only, perhaps. I want to build the entire product,
start to finish, using clang.
That's why I needed to
I wrote:
Thanks in advance - we would like to get these changes checked in this
week.
Let me clarify this a bit - there are some bugs open against the
MacOS/clang hotspot build that need to be resolved before considering a
change-over to clang:
On Aug 13, 2013, at 3:00 PM, Tim Bell tim.b...@oracle.com wrote:
I wrote:
Thanks in advance - we would like to get these changes checked in this week.
Let me clarify this a bit - there are some bugs open against the MacOS/clang
hotspot build that need to be resolved before considering
Hi Tim,
On 24/07/2013 8:15 AM, Tim Bell wrote:
Hello everyone-
This is a small set of changes to switch from gcc to clang when building
So we already added support for clang as the compiler for hotspot - is
this just extending things to allow configure to select clang?
on MacOS, and also
On 07/24/13 04:43 AM, David Holmes wrote:
Hi Tim,
On 24/07/2013 8:15 AM, Tim Bell wrote:
Hello everyone-
This is a small set of changes to switch from gcc to clang when building
So we already added support for clang as the compiler for hotspot - is
this just extending things to allow
On 2013-07-23, at 7:38 PM, Tim Bell tim.b...@oracle.com wrote:
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
On Jul 24, 2013, at 5:12 PM, David Chase david.r.ch...@oracle.com wrote:
On 2013-07-23, at 7:38 PM, Tim Bell tim.b...@oracle.com wrote:
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
On Jul 24, 2013, at 5:15 AM, Tim Bell tim.b...@oracle.com wrote:
On 07/24/13 04:43 AM, David Holmes wrote:
Hi Tim,
On 24/07/2013 8:15 AM, Tim Bell wrote:
Hello everyone-
This is a small set of changes to switch from gcc to clang when building
So we already added support for clang as
Christian:
That's not true. I've added Mac OS X support with the same change.
For building hotspot only, perhaps. I want to build the entire product,
start to finish, using clang.
That's why I needed to touch these files:
common/autoconf/hotspot-spec.gmk.in
common/autoconf/toolchain.m4
On 25/07/2013 8:48 AM, Tim Bell wrote:
Christian:
That's not true. I've added Mac OS X support with the same change.
For building hotspot only, perhaps. I want to build the entire product,
start to finish, using clang.
That's why I needed to touch these files:
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-
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.
21 matches
Mail list logo
