Re: CLANG special case

I’ve assigned the bug to me and will verify… > On Oct 6, 2015, at 9:23 AM, Jim Laskey (Oracle) > wrote: > > Since we are will to live with the de-optimization now, we should just remove > the condition until proven otherwise. > > >> On Oct 6, 2015, at 4:17 PM,

Re: CLANG special case

Since we are will to live with the de-optimization now, we should just remove the condition until proven otherwise. > On Oct 6, 2015, at 4:17 PM, Staffan Larsen wrote: > > When we upgraded to clang 6.3, I verified that the problem still existed. > See:

Re: CLANG special case

When we upgraded to clang 6.3, I verified that the problem still existed. See: https://bugs.openjdk.java.net/browse/JDK-8077364 which has pointers to the two tests that fail without the workaround. /Staffan > On 6 okt 2015, at 17:38, Phil

CLANG special case

I’ve updated to El Capitan and, of course, builds fail, and, of course, I modify hotspot/make/bsd/makefiles/gcc.make one more time and… I think this conditional clause should be removed at the very least (commenting to indicate needs investigation), or someone should research and see which

Re: CLANG special case

Ideally hotspot would review this, not build. so it would be helpful if hotspot found an engineer to own the bug :- https://bugs.openjdk.java.net/browse/JDK-8138820 So far as I know this is not tracked under any other bug id. -phil. On 10/06/2015 05:30 AM, Jim Laskey (Oracle) wrote: I’ve