2012-11-20 19:18:44 < Skyler_> BugMaster: which was the test you wanted me to run on the kaveri(?) ?
2012-11-20 19:18:50 < Skyler_> something to do with XSAVEOPT
2012-11-20 19:19:09 < BugMaster> cpuid eax = 7 ecx = 1
2012-11-20 19:23:12 < BugMaster> wait
2012-11-20 19:24:40 < Skyler_> 28b030 28b034 28b038 28b03c
2012-11-20 19:24:50 < BugMaster> eax = 0dh (13) not 7
2012-11-20 19:25:19 < Skyler_> okay
2012-11-20 19:27:25 < Skyler_> nvm, I am horribly dumb and obviously not in my right mind this morning, I forgot to give printf its arguments
2012-11-20 19:27:32 < Skyler_> eax=0xd, ecx=0x1 gives 0 0 0 0
2012-11-20 19:27:34 < BugMaster> btw. what you posted looks like pointers
2012-11-20 19:28:13 < BugMaster> hm. all zeros. than that is probably no bdver3
2012-11-20 19:28:43 < Skyler_> are we sure?
2012-11-20 19:30:05 < BugMaster> not sure but according to
http://gcc.gnu.org/git/?p=gcc.git;a...77aff08fc23d66b6eeb8a68c3d5c784f6ec6d07a#l545 that was one of the ways to find you if it run on bdver3
2012-11-20 19:30:21 < BugMaster>
http://gcc.gnu.org/git/?p=gcc.git;a...77aff08fc23d66b6eeb8a68c3d5c784f6ec6d07a#l467
2012-11-20 21:08:17 < Mandarinka> regarding the AMD ES discussion... in their Hot Chips 2012 slides, AMD claims that Steamroller module will have increased L1 instruction cache size. Of course, it'S not guaranteed, but perhaps it could help to identify the core
2012-11-20 21:08:36 < Mandarinka> sadly the slide isn't specific.
2012-11-20 21:10:11 < Skyler_> the chip says
2012-11-20 21:10:14 < Skyler_> 4x16kb data cache, 4-way
2012-11-20 21:10:19 < Skyler_> 2x64kb instruction cache, 2-way
2012-11-20 21:10:23 < Skyler_> 2x2048kb L2 cache, 16-way
2012-11-20 21:10:28 < Skyler_> according to puc-z
2012-11-20 21:10:30 < Skyler_> *cpu-z
2012-11-20 21:10:58 < Mandarinka> 64kb, that sounds like Bulldozer/Piledriver, doesn't it.
2012-11-20 21:11:23 < Mandarinka> unless cpu-z doesn't read the actual sizes but instead guesses based on older chips - no idea how it poperates
2012-11-20 21:11:38 < Mandarinka> *operates, sorry
2012-11-20 21:12:14 < Skyler_> I'm guessin it's a bulldozer then... ugh
2012-11-20 21:13:26 < Skyler_> *guessing
2012-11-20 21:13:54 < Mandarinka> there was some leaked information that AMD postponed Kaveri and will instead only introduce a refreshed Trinity APU (but that was based on desktop roadmap). On this monday, some site reported that AMD cancelled both Steamroller and the Excavator arch that comes after it
2012-11-20 21:14:39 < Mandarinka> AMD denied that but what do we know...
2012-11-20 21:14:48 < Skyler_> semiaccurate was the one reporting that though
2012-11-20 21:14:57 < Mandarinka> yeah
2012-11-20 21:14:57 < Skyler_> they are known for being... very speculative
2012-11-20 21:15:02 < Skyler_> (and often extremely wrong)
2012-11-20 21:15:28 < Mandarinka> yes, but they did get some thing right too, so it can'T be discounted completely
2012-11-20 21:15:30 < kierank> how come amd were being so opaque to you about the chip
2012-11-20 21:15:44 < Skyler_> left hand doesn't know what the right hand's doing
2012-11-20 21:15:50 < Mandarinka> with AMD, the worst thing imaginable usually tends to happen
2012-11-20 21:16:40 < Mandarinka> the Trinity refresh was supposed to be called Richland though, I didn't expect them to put the Kaveri name on it (their roadmap from this summer clearly promised GCN + Steamroller + 28nm for Kaveri)
2012-11-20 21:18:32 < Mandarinka> so there are no meassurable performance improvements above Trinity/Piledriver either? /unless you prefer to keep that secret, which I'd respect/
2012-11-20 21:18:41 < Skyler_> I haven't done detailed benchmarks
2012-11-20 21:18:47 < Skyler_> and probably shouldn't publish any
2012-11-20 21:19:24 < Mandarinka> yeah, I think so too
I was already surprised I learned what I saw in the log