From: Peter Zijlstra <peterz@infradead.org>
To: Jirka Hladky <jhladky@redhat.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Kamil Kolakowski <kkolakow@redhat.com>
Subject: Re: Kernel 4.7rc3 - Performance drop 30-40% for SPECjbb2005 and SPECjvm2008 benchmarks against 4.6 kernel
Date: Wed, 22 Jun 2016 09:54:45 +0200 [thread overview]
Message-ID: <20160622075445.GW30927@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20160622074941.GV30927@twins.programming.kicks-ass.net>
On Wed, Jun 22, 2016 at 09:49:41AM +0200, Peter Zijlstra wrote:
> On Wed, Jun 22, 2016 at 09:16:01AM +0200, Peter Zijlstra wrote:
> > WTF a benchmark needs that crap is beyond me, but whatever, I have
> > numbers.
>
> Oh, shaft me harder, its XML shite :/ How is a sane person ever going to
> get numbers out.
>
> I'm >.< close to giving up on this site and declaring the thing
> -EDONTCARE.
OK, done.. have a look at this:
/tmp/SPECjvm2008/compiler.compiler/compiler/src/share/classes/javax/lang/model/element/Name.java:54: cannot access java.lang.CharSequence
bad class file: spec.benchmarks.compiler.SpecFileManager$CachedFileObject@1c06fce6
bad constant pool tag: 18 at 10
Please remove or make sure it appears in the correct subdirectory of the classpath.
public interface Name extends CharSequence {
^
ERROR: compiler exit code: 1
Warmup (120s) begins: Wed Jun 22 09:45:33 CEST 2016
/tmp/SPECjvm2008/compiler.compiler/compiler/src/share/classes/javax/lang/model/element/Name.java:54: cannot access java.lang.CharSequence
bad class file: spec.benchmarks.compiler.SpecFileManager$CachedFileObject@1c06fce6
bad constant pool tag: 18 at 10
Please remove or make sure it appears in the correct subdirectory of the classpath.
public interface Name extends CharSequence {
^
/tmp/SPECjvm2008/compiler.compiler/compiler/src/share/classes/javax/lang/model/element/Name.java:54: cannot access java.lang.CharSequence
bad class file: spec.benchmarks.compiler.SpecFileManager$CachedFileObject@1c06fce6
bad constant pool tag: 18 at 10
Please remove or make sure it appears in the correct subdirectory of the classpath.
Clearly this stuff just isn't made to be used.
/me goes do something useful.
next prev parent reply other threads:[~2016-06-22 7:54 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 16:38 Jirka Hladky
2016-06-16 17:22 ` Peter Zijlstra
2016-06-16 23:04 ` Jirka Hladky
2016-06-21 13:17 ` Jirka Hladky
2016-06-22 7:16 ` Peter Zijlstra
2016-06-22 7:49 ` Peter Zijlstra
2016-06-22 7:54 ` Peter Zijlstra [this message]
2016-06-22 9:52 ` Jirka Hladky
2016-06-22 11:12 ` Peter Zijlstra
2016-06-22 12:37 ` Jirka Hladky
2016-06-22 12:46 ` Jirka Hladky
2016-06-22 14:41 ` Jirka Hladky
2016-06-22 20:59 ` Peter Zijlstra
2016-06-22 8:20 ` Jirka Hladky
2016-06-23 18:33 ` Peter Zijlstra
2016-06-23 18:43 ` Peter Zijlstra
2016-06-24 7:44 ` Jirka Hladky
2016-06-24 8:08 ` Peter Zijlstra
2016-06-24 8:20 ` Jirka Hladky
2016-06-24 12:02 ` Peter Zijlstra
2016-06-24 12:09 ` Jirka Hladky
2016-06-24 12:30 ` Peter Zijlstra
2016-06-24 12:35 ` Jirka Hladky
2016-06-24 12:44 ` Vincent Guittot
2016-06-24 13:08 ` Jirka Hladky
2016-06-24 13:09 ` Peter Zijlstra
2016-06-24 13:23 ` Vincent Guittot
2016-06-24 13:33 ` Peter Zijlstra
2016-06-24 13:45 ` Peter Zijlstra
2016-06-24 13:42 ` Peter Zijlstra
2016-06-24 15:54 ` Peter Zijlstra
2016-06-24 22:13 ` Jirka Hladky
2016-06-22 7:37 Branimir Maksimovic
2016-06-22 8:25 ` Jirka Hladky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160622075445.GW30927@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=jhladky@redhat.com \
--cc=kkolakow@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®