> 1 juni 2018 kl. 23:53 skrev Erik Joelsson :
>
> We need to add compilation flags for disabling speculative execution to our
> native libraries and executables. In order to allow for users not affected by
> problems with speculative execution to run a JVM at full speed, we need to be
> able
/Magnus
> 1 juni 2018 kl. 23:53 skrev Erik Joelsson :
>
> We need to add compilation flags for disabling speculative execution to our
> native libraries and executables. In order to allow for users not affected by
> problems with speculative execution to run a JVM at full speed, we need to b
The actual changes look good to me.
As a follow up, I think we should check if we could remove some of the JDK
prefixes that was in place just to differentiate from the JRE. The term JDK is
so overloaded, so it would be good to get rid of it where possible (as in "JDK
image", which should be o
JREs are a very long tradition. I suggest deferring disruptive changes
like this to some release past jdk11.
On Fri, Jun 1, 2018 at 3:02 PM, Erik Joelsson
wrote:
> Since JDK 9 and modules, the idea of a prebuilt JRE is no longer providing
> much value. The idea is rather that you link together
Looks good. The build is much simplified.
Modules.gmk
include_in_jdk can be removed since it should always be true.
In fact build.properties support can be removed some day.
Mandy
On 6/1/18 3:02 PM, Erik Joelsson wrote:
Since JDK 9 and modules, the idea of a prebuilt JRE is no longer
prov
Since JDK 9 and modules, the idea of a prebuilt JRE is no longer
providing much value. The idea is rather that you link together an image
with the modules and settings you actually need, either with or without
your application. For this reason oracle will no longer ship JRE images
that differ c
On 06/01/2018 10:53 PM, Erik Joelsson wrote:
> This patch defines flags for disabling speculative execution for GCC and
> Visual Studio and applies
> them to all binaries except libjvm when available in the compiler. It defines
> a new jvm feature
> no-speculative-cti, which is used to control wh
We need to add compilation flags for disabling speculative execution to
our native libraries and executables. In order to allow for users not
affected by problems with speculative execution to run a JVM at full
speed, we need to be able to ship two JVM libraries - one that is
compiled with spec
Hi , my change 8202322 just handled the fact that the visibility -
flags are not supported with xlc 12.1 , so setting them generated a TON
of compile - time warnings .
The introduction of the "-qvisibility=hidden"came with the mapfile
removal changes :
8200358: Remove
Hi Ichiroh,
we do not use the XLC 13 compiler on AIX yet here at SAP and I believe nobody
of my colleagues has played with it yet. So you are on a new playground here 😊
However, I believe the idea in OpenJDK with the abolition of map files is that
symbols should be invisible externally unless t
Sounds OK to me. :)
Best Regards
Adam Farley
Philip Race wrote on 01/06/2018 03:04:12:
> From: Philip Race
> To: Adam Farley8
> Cc: 2d-dev <[email protected]>, build-dev [email protected]>, Andrew Leonard ,
> "Stuefe, Thomas"
> Date: 01/06/2018 03:04
> Subject: Re: [OpenJDK 2D-D
11 matches
Mail list logo
