AMD CPU speculation... and expert conjecture

Page 322 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Status
Not open for further replies.
On another note, how did the "Steamroller" thread get turned into "ARM vs x86"???

It started off as a comment about how AMD is looking to develop some ARM CPU's. Some people took this as meaning ARM will replace x86 as the desktop CPU of choice. Was some dialog about computing and how each uArch has it's strengths and weakness's. It has since turned into a distraction. Currently there can be no resolution as it's pure speculation of chips that don't exist yet. I do ask that each party respect the others opinion and desist from this page long quote pyramids.
 


I must be writing in Chinese, because I have just said you that efficiency is irrelevant for ordinary desktops.

Also AMD is replacing x86 servers by ARM servers next year.
 
^^ AMD is releasing an ARM based server cpu, not replacing anything. Its a co-existence, a concept that seems impossible for some people to grasp.

http://www.techpowerup.com/190597/amd-expands-elite-mobility-apu-line-up-with-new-quad-core-processor.html

•Up to 172 percent more CPU performance-per-watt and up to 212 percent better graphics performance-per-watt than the previous generation;

that doesn't look like jaguar or low power x86 is getting canceled or replaced any time soon.

While (Juanrga = wrong) {printf("JUANRGA IS NEVER WRONG")};
 


Are you kidding? The paper is signed by three people and the senior author is Karthikeyan Sankaralingam, head of the Vertical Research Group, which is closely related to Intel.



No. I started explaining first why the article was biased pro-Intel. Then driven by curiosity I did search info about the authors and found that are closely related to Intel.

You ignored the early part of my arguments, the part about the article defects, and you took only the last part of my arguments, that part about the authors, which you reproduced and replied in the first place, inverting my real argument and even the order of my message. I wonder why...



No. I have said you that _if_ the article was right and Intel did really compete with ARM, then Intel had not cheated benchmarks this year.

The article is biased pro-intel. And Intel couldn't compare its new chip against ARM under fair rules. That is why Intel did cheat Antutu benchmarks this year.



Are you kidding again? First I am not saying that any x86 maker cheats. I am saying that _Intel_ does. Therefore, if you have _some_ ARM maker that cheats report it, but not try a anti-ARM argument like that.

Second, that is Anandtech. The same site that uses biased benchmarks as SYSMARK for favouring Intel, the same site that has been for years announcing how Intel did beat ARM (but never did), the same site that has presented Intel mobile benchmarks this year, where the Intel chip was running inside a refrigerated room for allowing the chip to run benchmarks at maximum turbo freq. OK?

Third, the article says something completely different to what you pretend. It is not about cheating benchmarks code (as Intel did with Antutu), it is about if products run at turbo freq. when running benchmarks, or not.

Fourth, I can see lots of chipmakers with with a big "N" all the table cells. The "N" mean _NO_. Look at Nexus 4 or to Tegra 4 for example. They both play honest.



I also. Tegra 3 is about 2x faster and about 40% more efficient, for instance. AMD bulldozer would rise power consumption and ruin the efficiency that they report for x86...



Recall this was made at 2012. Tegra 3 was available and they rejected it.

The 'old' SB i7 is only slightly behind the modern IB i7, and this one is basically on tie with the last HW i7. On the other hand a A15 is _much_ faster and efficient than A9, and A57 is _much_ faster and efficient than A15.

E.g. the A15 is ~70% faster than A9, whereas reducing power consumption.

The conclusions in their paper are wrong.



They would bother because would ruin their conclusions about x86. And this would ruin Intel plans to sell x86 phones, servers, tablets...



I didn't say that GCC favours intel. Their choices when compiled code did.



We know that ARMv8 improves performance and efficiency. Their claim to __news__ sites that it doesn't matter reflect either ignorance or bias.



Repeating it will not make it true. The paper was written by 3 authors one of them is Karthikeyan Sankaralingam, who is _not_ a student, but the head of a research group closely related to Intel.



I already explained you how Intel cheated SYSMARK benchmark with AMD, Nvidia and VIA being part of the SYSMARK consortium. Therefore, your argument is lacking.



1000x is the scale factor between peta and exa. The goal is not to obtain one exaflop and stop there. The goal is to move the entire petaflop range of supercomputers to the exaflop range. This means 1 peta --> 1 exa and 50 peta --> 50 exa approx.



Now you look as an Intel representative ;-) but my point remains: x86 is a marketing trick for the Phi, because it doesn't run the same native x86 binaries that an 3770k, for instance, and because most (all) of its performance comes from using Intel Phi specific _extension_ of the x86 ISA.



Nope. I have said you that Nvidia "project Denver" _core_ is aimed to supercomputers. No that Tegra 6 was.

You can have the same _core_ in different chips aimed to different markets. We will see phone chips with one or two A57 cores inside. But we will not see any phone with an AMD Seattle chi, despite Seattle uses A57 cores, because Seattle is for servers.

Montblanc project is using available mobile chips for prototyping. The final supercomputer will use ARM chips similar to the ARM servers, but _no_ mobile chips.
 


I have explained this before. Either you cannot read or you are doing it deliberately. Once again:

AMD is replacing the jaguar-based servers by ARM-based servers. This is happening at 2014.

AMD has claimed how all the future servers will be ARM-based. Feldman has explained why customers want ARM to win.

AMD has also claimed that they are releasing the new x86 based Warsaw servers only for institutional customers that will be slow on migrating to ARM. To be read as, once all our customer migrate to ARM we will not release x86 servers anymore.

AMD will be also replacing jaguar-based tablets by ARM-based-tablets this or next year.
 


AMD's clarification:

http://www.techpowerup.com/192552/amd-explains-why-mantle-doesnt-work-on-xbox-one.html

Additionally, I am not at all surprised it's not on XBone, PS4 hasn't said one way or the other; though judging by AMD's clarification it likely isn't.

However, it accepts HLSL, so you wouldn't have to recode, just basically would recompile it sounds like. Not as massive an issue as you want to make it seem...and it will still simplify console to PC ports, because the DX calls and programming can be ported to MANTLE with very little effort.
 


Show me one piece of material from AMD directly that is worded "ARM will replace X"...I can't find one...sounds like more tinfoil hats and speculation. This thread has become full of that lately.

I would say it's almost to the point that this thread needs an enema.

This is what AMD has had to say about it:

http://www.xbitlabs.com/news/cpu/display/20121130040403_AMD_Expects_x86_to_Remain_Important_Architecture_for_25_30_Years.html

Although Advanced Micro Devices recently announced plans to design various system-on-chips based on ARM architecture, the company believes that the x86 instruction set will remain very important for the industry for decades to come. Quite possibly, the claim was made to debunk rumours about AMD’s plans to halt development of high-performance x86 chips in a bid to concentrate on low-power products.

http://www.electronista.com/articles/12/06/13/arm.core.to.operate.alongside.x86.cpu/

AMD has confirmed plans to license ARM technology for chipsets in upcoming 'ultrathin' notebooks. The company is stopping short of replacing its x86-based CPU and GPU components, however, as an ARM Cortex-A5 chip will serve as an independent core tasked with running applications in a secure environment via ARM's Trustzone technology.

http://hardware.slashdot.org/story/13/09/10/1558205/amd-reveals-roadmap-for-arm-and-x86-socs

"On the eve of the Intel Developer Forum in San Francisco, AMD unveiled what it calls an ambidextrous embedded roadmap, based on a series of new system-on-chip (SoC) and accelerated processing unit (APU) products built from both ARM and x86 CPU cores. Planned for launch in 2014 are an ARM Cortex A57-based 'Hierofalcon' SoC, a 'Bald Eagle' APU using a new 'Streamroller' x86 CPU, a multi-core x86 'Steppe Eagle' APU, and an 'Adelaar' discrete Embedded Radion GPU. 'There are different customer needs in different segments of this market, from low-power to high-performance, Linux to Windows, and x86 to ARM,' commented Arun Iyengar, VP and general manager, of the AMD Embedded Solutions division."

Show me where it says "replace"...because they never said that.

 




Still good news, but to begin with that was the whole purpose of MANTLE... they said it since day 1 that MANTLE was not supposed to compete with other API`s but to make Porting to PC faster and cheaper which will relate in Great Ports from Consoles to PC.

It`s MANTLE by the way... not MANTEL... unless you are doing it in on purpose as a mock?
 


Little modification is still a modification (and testing and extra time and cost), so I won't start celebrating just yet.

AMD has to be very cautious on how it plays the cards from now on.

The more news are out, the hard it is for me to see a good ending for MANTLE. I think if Valve says they'll support it, it will get a mayor backer in play. Hope they say something soon.



Well, so far gamerk loves to be on his own ways, so he'll prolly won't stop calling it like that ever, haha.

Cheers!
 
What is the licensing on HLSL? Does Microsoft control where HLSL can be used, and if it does, would that be a problem for Mantle on Steam Boxes?
 


HLSL = High Level Shader Language, it's something akin to C++ in graphic terms. So, while MS can make DX run only on HLSL, they cannot limit what else accepts it as a programming language for 3D acceleration hardware calls.
 


Yep coders are gonna write for DX and just call it a day. There may be a few publicity releases here and there but I don't expect it to last more then a generation or two. It's simply not economical to spend time coding for a subset of your customer base, not with the deadlines software developers work on.

I now consider this API DoA.
 

It would have had potential, but oh well..
 


MANTEL isn't supported on PC either. :lol:

If you refer to MANTLE, well AMD said, during presentation, that it is for PCs, not for consoles. Anandtech said that MANTLE was just the XB1 API, but this couldn't be true. Eurogamer said that MANTLE would be close to the low-level API on the PS4 ("close" doesn't mean "the same").

AMD also said that MANTLE is aimed to (i) simplify the porting from consoles to PCs and (ii) provide console-like optimizations to PCs.



Rocks, you continue using _double standards_. For instance, you didn't provide us any piece of material from AMD saying "We will release FX Steamroller for AM3+ platfform", but you have been saying to everyone on the forums how one could purchase a FX Piledriver plus an AM3+ mobo now and upgrade to Steamroller FX 8-cores latter using the same mobo.

I have not provided you a quote with the exact selection of words that you want to hear, but I have provided you (i) official roadmaps and server plans showing how Seattle replaces Opteron-X, (ii) the "ARM will win" secret slide from AMD, and (iii) quotes such as

He [Feldman] also told us that “Warsaw”, AMD’s follow up in the 2P/4P server market, will cater for a declining but still large market with institutional customers that will take longer to migrate to an ARM ecosystem.

What part of migrating to ARM you don't still understand?

I reproduce the slide again

why-arm-will-win.jpg





That is an old quote from 2012. Of course, the x86 instruction set will remain very important for the industry for __legacy workloads__. LOL many bussiness are still using Windows XP, but this doesn't mean that XP is the future, neither that Microsoft is releasing XP updates anymore.

AMD is releasing "high-performance x86 chips", namely 12/16 core Warsaw CPUs, but this is based in Piledriver, because it is only for legacy x86 workloads. Again read what AMD has said about Warsaw.

If you want know Rory's plans for the future, take a look to this recent interview:

Rory expects semi-custom silicon to see heavy use in these new markets by the way. Lower cost typically means lower margin, which is something the new AMD is ok with. Making Intel margins (or even traditional AMD margins) is tough, in these new markets AMD just needs to be making better margins than the ARM players as the company transitions from being fully PC supported, to PC + additive revenue from these new markets and finally to a position where AMD’s revenues are dominated by these new revenue sources. What are the new markets in specific? Getting anyone at AMD to answer that question today is tough, but I suspect the first place to look is among all of those other players I talked about earlier. The companies tasked with competing with these vertically integrated powerhouses could rely heavily on AMD.

http://www.anandtech.com/show/7281/understanding-amd-semi-custom-strategy




Unrelated.



Seattle replaces Opteron-X. Your link is about Hierofalcon != Seattle.
 


I find it extremely interesting that you use the same silly term, DoA, than ExtremeTech. At least they report how several sources are saying them that the difference between MANTLE and XB1 API is minimal. That minimal difference accounts for the custom hardware on XB1 and for the OS differences.
 


Microsoft control the HLSL compiler apparently - is AMD writing its own?

Another crucial difference between HLSL and GLSL (I don't know CG so I can't speak for it) is that with HLSL Microsoft provide the shader compiler as part of the D3D runtime whereas with GLSL your hardware vendor provides it as part of their driver.

This has advantages and disadvantages on both sides.

With the GLSL method the vendor can tune the compiler to the capabilities of their hardware. They know their own hardware best, they know what to do and what not to do. On the other hand the disadvantage is that - in a world where there are multiple hardware vendors - you have a situationwhere there can be inconsistencies between shader compilers, and the vendor also has complete free reign to screw up.

With the HLSL method Microsoft control the compiler. Everyone is on a consistent tech base, and if a shader compiles successfully in one place then it can be reasonably supposed to compile everywhere. The same shader will produce the same compiled output irrespective of vendor (all other things being equal of course). On the other hand the HLSL compiler has to be a "works consistently on everything" thing, so it's not able to pull any special vendor-specific tricks to get the last few drops of juice out of the tank.

... from http://gamedev.stackexchange.com/questions/4234/what-are-the-pros-and-cons-of-hlsl-vs-glsl-vs-cg

If 99% of mantle is in the HLSL compilation, then there would be very little work needed to convert an application from pure D3D to Mantle.
 




Which is exactly the code that gets replaced during a port. But no one is going to spend the time to do an OGL/libgcm backend for the PS4, DirectX11 backend for the XB1, and then also implement a Mantle backend on the PC that only benefits the third place GPU maker. Its not happening. You'll see a few press releases, but that's about it.

Mantle is dead on arrival.
 
So much anger over Mantle. If AMD is going to pay DICE and whatever to add Mantle support, I don't see how it's DoA when PhysX has been around forever.

The writing is on the wall. Game developers want out of Windows, and Mantle is a tool to help make that possible. A huge problem with gaming in Linux is DirectX support. WINE does DX9 and that's it. There is no good way of making it work. Valve has a wrapper to translate API calls from DX to OpenGL but it's just needless overhead, specially compared to Mantle.

GamerK, I do feel you're missing the point. Linux has a less than 1% market share, yet Valve is pushing Steam on Linux so hard that they've gone as far as to make their own distribution of Linux.

EA and DICE are already talking about how it just would take ONE big game to get Linux as a viable gaming OS. And EA has had some foresight and used QT for Origin, which is a very easy to port platform. Why did they not use .net since Visual Studio is so good? They used QT so they could port it to different OSes. Even Android has some sort of QT support. It's (obviously) there on Windows, and it is good on BSD, Linux, OSX, iOS, Windows CE, and there are even external ports for more obscure OSes like Haiku.

So, if MS and Windows environment is so great, why did EA go out of its way to use QT?

Do you see now? A lot of developers want out of Microsoft. They are scared of what is happening with Windows 8 and how that is going to affect PC gamers. They see how Intel and Nvidia are pushing for a closed ecosystem of disposable devices which can't be upgraded (hurray for profitability through restrictions!) and they want to keep the gaming PC platform alive. It is growing at a staggering rate, yet MS and Intel want it DEAD because it's not making them as much money as you could make selling fruity toys (note how Apple is worth more than Intel right now, mainly due to a phone while Intel's technological achievements are far greater).

Mantle makes it a lot easier to get your games out of the Windows ecosystem. Companies like Valve don't care about market share, they want out of Windows badly and they'll take any tools they can to get away from where Windows is heading.

It also works out quite well for Intel as well. Their CPUs have been perfectly acceptable in high end gaming rigs for the last 5 years (meaning an i7 920 with a little overclock could still power a good gaming system just fine without massive bottlenecking). For every CPU sale Intel sees in a gaming PC, they more than likely see at least two graphic card sales go to Nvidia and AMD.

You're here ranting about how market share is the defacto goal of game developers right now, and you're doing so because you're (incorrectly assuming like always) that because game developers have always went for the bigger market shares first, that they always will.

If that is still the case, and we're not at the foothills of a mountain of change, then why is both Nvidia and AMD investing so much in Steam Machines to run Steam OS? Why are we seeing AMD go as far as to create a new API that's compatible with DX in some ways, yet is cross platform (ergo Linux and OSX if the consoles are removed from the equation).

You are completely missing what is going to happen. AMD gaming PCs is a huge market for them. They have very little in professional workstations. They don't have much in mobile outside of Jaguar. Their bread and butter is PC gaming. Even their APUs are sold under the guise of affordable gaming platforms.

You are really, really missing the point of Mantle and what Nvidia and AMD are BOTH trying to do. They want out of the Windows future. Where Microsoft is directly competing with hardware that don't make a good platform for what both Nvidia and AMD depend on for large amounts of money (dGPUs and APUs).

So please, really, stop with the "THIRD PLACE LOL!" and market share remarks. We're seeing companies make moves to get away from Windows, and to do so means that they're going to have to take the risk of pushing markets with little market share.

I don't really care where the marketshare of GCN ends up. In gaming PCs, it's definitely got much more market share than Linux does, and Valve is pushing Linux really, really hard. Mantle is a tool to help with this, and AMD went as far as to keep it open so Nvidia can jump on it and implement it themselves if they want.

We already have gone from you implying this is some sort of massive API where games have to be completely coded from scratch to use it, and that no one will use it, to it being much more closer to a recompiler.

I really don't think you understand how much EA and Valve want out of the Windows ecosystem. They won't go OpenGL because it sucks for the most part, but they will definitely go Mantle if they can just recompile with different libraries and get a cross-platform package. It's even easier than an OpenGL port that way and it's going to be massively faster.

It's quite fun watching all the Wintel Nvidiots cry over Mantle and what's happening. I am quite sure you were one of those folks saying Steam on Linux was a disaster and DoA as well. I'm going to enjoy coming back to this post in a year or so and reading how someone like you can be wrong so many times.

AMD has made it quite clear that they are talking with game developers about what they want, and they're asking for tools to get away from Windows. Another massive assumption that you're making is that AMD is forcing this on game developers and studios. For all you know, they could have approached AMD themselves and said they wanted help getting away from DX and Windows.

We simply don't know and you're entire argument rests upon this assumption of which you have no proof of.

So, I hope you can kind of see what game studios want from this. They want cross platform. Indie developers want cross-platform (notice how fast they were to jump on Steam on Linux?) No one likes what MS wants and no one wants to be bound to an ecosystem where your host for that ecosystem is trying to build a vertical stack that runs from hardware to software in house. Specially if you're a hardware manufacturer. Specially if you're a game developer releasing on a platform that is so ill-received by gamers as Windows 8 with metro and knowing that you're basically at the mercy of MS's choices and you have no other options.

So really, just stop already. You have a huge problem with assuming that things that happened in the past will continue to happen no matter what. You do it with multi-threading, you do it with APIs, you do it with EVERYTHING. I realize it works sometimes, but if that's all you do you're limiting your foresight massively.
 
Nice post blackstar, but gamerk and palladin do have an important point: from the inside of the development cycle and a business point of view, it doesn't make sense to have yet another API that you have to prepare developers for. It does cost time and money to use a new API in terms of development, testing (QA) and time-to-market.

I also believe what you say, since the trend (from Valve and AMD) have been to put more tools in the hands of developers to part ways with Microsoft as much as they can. Hope Google can give Valve and AMD a hand as well (for instance, announcing that MANTLE can be had within the Android kernel and selected devices) for the sake of competition (fragmentation as well as a by-product).

Hell, we all win with this, no matter whether you like MANTLE or not. If it succeeds and is adopted widely (including nVidia) then we will have great performing games in our hands down the road that make use of you hardware with great efficiency in a lot of platforms (Linux, Windows, OS X, iOS, Android, etc). If its not, it will depend on Microsoft entirely. Now, it looks like there has been a "heads up" with Valve and now MANTLE inside their HQ, so we will see more of what will happen with Windows and DirectX sooner than we might expect. I'm sure MS can keep the Windows reign by just making DirectX better than what it is now. No matter how we'd like AMD and Valve to make the Windows reign fall, Microsoft is still a huge empire with a lot of resources. Especially since Valve and AMD don't seem to be joining forces yet. I really believe nVidia won't give a darn about any outcome as long as they keep making money, haha.

More interesting times ahead.

Cheers!
 
I think some people are confused here, they think MANTLE was some sort of DX Alternative... which is not, it was just meant to make fast and affordable ports to PC with GREAT PERFORMANCE.

No one should care if Xbone or PS4 wont be using it, the fact it... you are 10 times more likely to see a Good Port from Consoles to PC compared to this current gen is almost done.

In other words, MANTLE = GOOD PORTS in the Next Gen, I also saw several Devs throwing tons of shit at Microsoft... you don`t need to be a Genius to listen to what Devs are saying, and they want to get rid of MS.

A key point in here is IF VALVE will support, which will pretty much decide how long does MANTLE will last.


All i see for the Next Gen of Games (Console and PC) is GOOD NEWS, all thanks mostly to AMD and Valve partially... forget about the days of horrible ports to PC, this gen is going to be awesome for PC Gamers.
 


I wouldn't say it's DoA, you can easily recompile your HLSL DX commands into MANTLE commands from my understanding of it thus far (though I have no material from AMD on the matter, I expect we will get information once we do something on Frostbite though).

Additionally, the list of titles being done on Frostbite alone is mind bending.

Dragon Age series' next installment
BF4
Need for Speed series' next installment
Command & Conquer series' next installment
Mirror's Edge 2
SW Battlefront 3
Mass Effect series' next installment (ME4?)

EA uses this engine *A LOT*, for lots of AAA titles, which may very well drive a big partnership with MANTLE and push it heavily in the console to PC porting side of their publishing house. AMD was not selecting poorly when they chose the *LARGEST* publisher in all of video games as a partner to implement this with. EA is always looking for an advantage as well, so this could benefit both sides greatly.

EDIT: If they got just 1 more major publisher to push this...like Activision Blizzard or Bethesda or Valve, for example...they would likely ensure future adoption at a high level.

Any EA publishing partner would have access to this, and likely be persuaded to use it...
 


*applause*

I think you made the point I have been trying to push for a while, but was overlooked.

MANTLE does something no other API allows...

Compatibility with DX 11.2 for any OS.

gamerk: You talk about market share...what about people who could use Steam for Windows and Linux. Imagine the market share that recompiling could afford you by just adding additional OS support.

The first time MANTLE makes an otherwise Windows only franchise available on OSX and Linux, I think you'll see a huge adoption rate for these "lesser" OS systems.

If you could get BF4 on Origin for Linux because of MANTLE, don't think tons of Linux users who were formerly dual booting wouldn't uninstall Windows entirely.

Once that paradigm shift occurs, games supporting only DX will be left in the cold to shrinking market share. Sure the windows numbers will likely begin to dwindle slowly, however, the installed base of high end gamers switching to a better OS that's free will increase faster than the people who don't buy many PC Games and run Windows because "it's familiar". However, keep in mind, that's the same crowd that hates Win 8 for different reasons.

NVidia can pick up the MANTLE for the API too (pun intended), and basically bring DX to it's knees if they're smart. Steam boxes will definitely be a driving force in this. If steam boxes pick up pace and sell well, and Valve jumps on board with MANTLE, and we see BF4 ported to Linux using MANTLE, the contest may well have already been won.

yuka: I can understand your point, and theirs about business perspective.

However, M$ is on the wall leaning right now, if they were to stumble, the cataclysm of events that would lead directly to the destruction of their DT PC market share would be a perfect storm right now.

I am not going to forecast it, because *A LOT* has to go right; however, 2014 has the makings to actually be the year of the Linux gaming desktop. They've been saying it for years, and I always thought they were smoking something stronger than cigarettes; however, the pundits may finally be right...after 15 years of guessing.

We could see the fall of M$ from the near monopolistic grip they have on DT PC software within the next 1-2 years. They're losing mobile already, and have turned to services and devices to pick up slack...though they may just lose out on the one thing they thought they had locked in during the process of trying to put a stranglehold on the technological world across all avenues.

I am cautiously excited to watch the next 6-12 months unfold and see what the gaming industry offers up. This could, very well, be the day some thought would never come, and we may see the dethroning of the DT OS king.
 
What AMD is trying to push is a half way point for mantle to bridge console APIs and PC directX. It will leverage GCN in consoles, which run low level code and bring that low level code to all GCN cards. Which means if a developer wanted to, they could get the game to run in mantle much faster than getting it to run on all PC, then go back and port to DX11. It like how C++ was compiled into C before compiled into assembly. There is a bridge that makes it easier.
 
Amd Gaming Evolved Program? Lately we seen quite a bit of games that had a AMD logo on it if Amd keeps that up why wouldn't they ask those dev's(money) to support mantle once they get it started it won't be much more to add.
 
Status
Not open for further replies.