> On Aug 24, 2016, at 9:26 PM, David Holmes wrote:
>
> Hi Kim,
>
> Sorry this fell off the radar …
That’s okay. There was a long gap while I was working on other things.
> On 24/08/2016 7:09 AM, Kim Barrett wrote:
>> Mandy asked for some additional comments to make
Hi All
Please take a look at
http://cr.openjdk.java.net/~weijun/8164705/webrev.00
From the beginning of JDK, FilePermission canonicalizes the input path
and use the result in implies() and equals(). This has been a big
performance hurt and leads to confusing results when symlinks are
John,
This is useful, thanks. Probably more questions will follow after doing more
homework.
Mandy
> On Aug 24, 2016, at 10:07 AM, John Rose wrote:
>
> On Aug 22, 2016, at 9:30 PM, Mandy Chung wrote:
>>
>> We need to follow up this issue to
Hi Kim,
Sorry this fell off the radar ...
On 24/08/2016 7:09 AM, Kim Barrett wrote:
Mandy asked for some additional comments to make life easier for
future readers. I've also stopped pretending the description for
waitForReferenceProcessing is javadoc, since this function is private
and only
> On 24 Aug 2016, at 15:48, Martin Buchholz wrote:
>
> Below it seems like weakCompareAndSetVolatile is susceptible to spurious
> failure as much as other weak cas variants and so should have the same kind
> of retry loop.
>
> {
>
Hi,
Recent discussion on the wrapping of exceptions (any Throwable) in LinkageError
be it for invokedynamic and BootstrapMethodError (a spec issue) or for
signature polymorphic linkage (an implementation detail AFAICT) resulted in a
more detailed look at the exception handling in the
Below it seems like weakCompareAndSetVolatile is susceptible to spurious
failure as much as other weak cas variants and so should have the same kind
of retry loop.
{
boolean success = false;
for (int c = 0; c < WEAK_ATTEMPTS && !success;
> On 24 Aug 2016, at 14:17, Martin Buchholz wrote:
>
> Hi Paul,
>
> Thanks for doing this.
>
> Probably your IDE is fixing import statements. We'd prefer having that not
> happen for j.u.c. but we can live with it.
>
Ah, i will update so as not to perturb that.
> Of
On Wed, Aug 10, 2016 at 5:03 PM, Paul Sandoz wrote:
>
> This touches 166 classes that use or refer to the weak plain/volatile
> methods.
>
Feel free to commit these. They will eventually break jsr166 CVS but we'll
deal with it.
Hi Paul,
Thanks for doing this.
Probably your IDE is fixing import statements. We'd prefer having that not
happen for j.u.c. but we can live with it.
Of course, keeping all the variants in sync is errorprone. Below is one
case where what you're testing and what your assertions say are out of
Thanks all! Pushed.
On Wed, Aug 24, 2016 at 1:06 PM, Paul Sandoz wrote:
>
> > On 24 Aug 2016, at 12:37, Martin Buchholz wrote:
> >
> > Let's get in the fix for regression 8163353 quickly:
> > http://cr.openjdk.java.net/~martin/webrevs/openjdk9/
>
> On 24 Aug 2016, at 12:37, Martin Buchholz wrote:
>
> Let's get in the fix for regression 8163353 quickly:
> http://cr.openjdk.java.net/~martin/webrevs/openjdk9/jsr166-jdk9-integration/ConcurrentHashMap-keySet-removeAll/
> https://bugs.openjdk.java.net/browse/JDK-8163353
On 24/08/2016 20:37, Martin Buchholz wrote:
Let's get in the fix for regression 8163353 quickly:
http://cr.openjdk.java.net/~martin/webrevs/openjdk9/jsr166-jdk9-integration/ConcurrentHashMap-keySet-removeAll/
https://bugs.openjdk.java.net/browse/JDK-8163353
Looks good, I think a couple of
+1
/Claes
On 2016-08-24 21:37, Martin Buchholz wrote:
Let's get in the fix for regression 8163353 quickly:
http://cr.openjdk.java.net/~martin/webrevs/openjdk9/jsr166-jdk9-integration/ConcurrentHashMap-keySet-removeAll/
https://bugs.openjdk.java.net/browse/JDK-8163353
Let's get in the fix for regression 8163353 quickly:
http://cr.openjdk.java.net/~martin/webrevs/openjdk9/jsr166-jdk9-integration/ConcurrentHashMap-keySet-removeAll/
https://bugs.openjdk.java.net/browse/JDK-8163353
On Aug 22, 2016, at 9:30 PM, Mandy Chung wrote:
>
> We need to follow up this issue to understand what the interpreter and
> compiler do for this unused slot and whether it’s always zero out.
These slot pairs are a curse, in the same league as endian-ness.
Suppose a
Hi,
LambdaForm predefines a number of forms for the benefit of the LF and
NF interpreters, which doesn't appear useful at all at this point.
JIRA: https://bugs.openjdk.java.net/browse/JDK-8164739
Webrev: http://cr.openjdk.java.net/~redestad/8164739/webrev.01/
Testing: all java/lang/invoke
Hi,
Gentle reminder.
Paul.
> On 10 Aug 2016, at 17:03, Paul Sandoz wrote:
>
> Hi
>
> Please review:
>
>
> http://cr.openjdk.java.net/~psandoz/jdk9/JDK-8162108-rename-weakCompareAndSetVolatile/webrev/
>
>
+1
On 2016-08-24 16:28, Srinivas Dama wrote:
Hi,
This patch fixes very small typo error.
Please review http://cr.openjdk.java.net/~sdama/8163793/webrev.00/ for
https://bugs.openjdk.java.net/browse/JDK-8163793
Regards,
Srinivas
+1
On 8/24/2016 7:58 PM, Srinivas Dama wrote:
> Hi,
>
> This patch fixes very small typo error.
>
> Please review http://cr.openjdk.java.net/~sdama/8163793/webrev.00/ for
> https://bugs.openjdk.java.net/browse/JDK-8163793
>
>
> Regards,
> Srinivas
Hi,
This patch fixes very small typo error.
Please review http://cr.openjdk.java.net/~sdama/8163793/webrev.00/ for
https://bugs.openjdk.java.net/browse/JDK-8163793
Regards,
Srinivas
> On Aug 24, 2016, at 3:50 AM, Per Liden wrote:
>
> Still looks good.
>
> cheers,
> Per
Thanks.
>
> On 2016-08-23 23:09, Kim Barrett wrote:
>> Mandy asked for some additional comments to make life easier for
>> future readers. I've also stopped pretending the
http://cr.openjdk.java.net/~redestad/8164483/webrev.02/
Looks good.
Best regards,
Vladimir Ivanov
Regarding LambdaForm.Kind, IMO field accessors push enum approach to the
limit. Let's think about better ways to represent LF shape in a
structured manner, but I'm fine with keeping it for
On 2016-08-24 13:02, Vladimir Ivanov wrote:
src/java.base/share/classes/java/lang/invoke/DirectMethodHandle.java
+@ForceInline
+/*non-public*/ static Unsafe unsafe() {
+return UNSAFE;
+}
+
+NF_unsafe = new NamedFunction(DirectMethodHandle.class
+
src/java.base/share/classes/java/lang/invoke/DirectMethodHandle.java
+@ForceInline
+/*non-public*/ static Unsafe unsafe() {
+return UNSAFE;
+}
+
+NF_unsafe = new NamedFunction(DirectMethodHandle.class
+
Looks good.
Best regards,
Vladimir Ivanov
On 8/23/16 11:57 AM, Claes Redestad wrote:
Hi,
this patch adds configurable link-time generation of the invoker forms.
Some such forms is commonly used early on in even the simplest startup
tests, and an unbounded number of invoker forms can be
On 24/08/2016 10:59, Claes Redestad wrote:
Agreed, seems like something to consider for a future release.
Thanks!
/Claes
PS. I still need a OpenJDK Reviewer before I can push this one
Looks okay, I guess I would name it Holder or something like that rather
than "Lazy" but that is a minor
+1.
-Chris.
On 23/08/16 21:52, Stephen Colebourne wrote:
This looks fine to me. I suspect that we could hand write a parser to
avoid the regex, but this probably suffices.
Stephen
On 23 August 2016 at 19:49, Claes Redestad wrote:
Hi,
this tiny cleanup reduces
Agreed, seems like something to consider for a future release.
Thanks!
/Claes
PS. I still need a OpenJDK Reviewer before I can push this one
On 2016-08-23 23:54, Stephen Colebourne wrote:
Really, we should add a TemporalAmountFormatter to the JDK, but its a
bigger piece of work and quite
Still looks good.
cheers,
Per
On 2016-08-23 23:09, Kim Barrett wrote:
Mandy asked for some additional comments to make life easier for
future readers. I've also stopped pretending the description for
waitForReferenceProcessing is javadoc, since this function is private
and only accessible via
On 2016/8/24 12:53, David Holmes wrote:
On 24/08/2016 1:39 PM, Hamlin Li wrote:
On 2016/8/24 11:02, Martin Buchholz wrote:
On Tue, Aug 23, 2016 at 9:17 AM, Martin Buchholz > wrote:
I didn't see this thread before updating the bug.
I
31 matches
Mail list logo