Gut feelings, happy thoughts and positive words of encouragement on tech forums do not pay the bills.
Neither does wild speculation on the viability of products very far down the line.
Gut feelings, happy thoughts and positive words of encouragement on tech forums do not pay the bills.
So Amur and Nolan have been axed. Unless they are renamed into Zen in 2016.
Thursday 11 December 2014
AMD is set to launch x86-based Nolan and ARM-based Amur tablet processors in the second half of 2015. The Nolan processors will feature an interface that is compatible with both ARM and x86-based products.
The Amur processors will feature ARM's Cortex A57 architecture and will support both Android and Linux operating systems.
Its gone from their own roadmaps.
There s a disclaimer at the bottom of any roadmap, including this one, beside the published RM is a six months shedule since Carrizos are to be released in H1 2015.
The roadmap is for 2014+2015. Its not specified anywhere that its only 6 months. Or does the disclaimer say anything about it.
Unless you can prove it otherwise with an AMD source. Then the products doesnt exist in 2015 and may not exist at all anymore.
The roadmap is for 2014+2015. Its not specified anywhere that its only 6 months. Or does the disclaimer say anything about it.
Unless you can prove it otherwise with an AMD source. Then the products doesnt exist in 2015 and may not exist at all anymore.
There was just an interview with an AMD exec that said 20nm would be out in 2015.
Mark Papermaster revealed that "we’ll continue to transition and we have our FinFET designs well underway, but we won’t be the first user, the bleeding edge of any new technology node. You will see us be a very, very fast follower, so we’re right on track with our FinFET designs and what you will see next year really is 28-nanometer and 20- nanometer products from AMD."
And since when does one single roadmap have to show every market?
they're also doing console chips on 20nm, I'm pretty sure. I don't doubt we'll see some 20nm non-console APUs released by the end of next year though--however, released doesn't necessarily mean widely available
like they are pretty much resigned to competing on price rather than cutting edge performance.
So Amur and Nolan have been axed. Unless they are renamed into Zen in 2016.
Once again you're just spreading fud. Posting wild speculation as fact. It appears if you have nothing facial and bad to say, you just start making things up!
Right, AMD just hides it from their roadmap for the fun of it.
Things disappear from AMD roadmaps all the time...yet we still end up seeing releases. (sometimes just not the way that we initially thought)
Examples?
And do you remember Wichita and Krishna APUs? They dissapeared because they got cancelled.
Carrizo L is announced less than 6 months before launch, where was the roadmap that announced it within a one year schedule.?.
Carrizo L is a new product, not a removed one.
float randgen(); // random number generator from 0 to 1 from the freely available Ranq2 PRNG as found in Numerical Recipes: The Art of Scientific Computing 3rd Ed. by Press et al - has period ~2^126
#pragma omp parallel for
for (int i=0; i < particles; i++) { // creates particle numbers of threads
particle[i].x = 0.0f; // starting position
particle[i].y = 0.0f; // starting position
particle[i].z = 0.0f; // starting position
for (int j=0; j < steps; j++) {
float newz = 2 x randgen() - 1;
float alpha = 2 * pi * randgen();
float r = sqrtf(1 - newz * newz);
particle[i].x = r*cosf(alpha);
particle[i].y = r*sinf(alpha);
particle[i].z = newz;
if(particle[i].z < 0) {particle[i].z -= particle[i].z;}
}
}
In response to claims that 3DPM is biased against AMD made by Abwx.
3DPM is written, at its base level, very simply.
A for loop is declared to be multithreaded, and the code within the loop deals with x/y/z co-ordinates for trigonometric transforms on a struct with three main float class members.
One of the algorithms looks like this, in mixed C++/pseudocode using OpenMP:
No effort was made to incorporate any advanced processor functions from any processor set. Compiler flags were set solely for speed, and faster versions of the trigs were used. Made in C++ with VS2012.Code:float randgen(); // random number generator from 0 to 1 from the freely available Ranq2 PRNG as found in Numerical Recipes: The Art of Scientific Computing 3rd Ed. by Press et al - has period ~2^126 #pragma omp parallel for for (int i=0; i < particles; i++) { // creates particle numbers of threads particle[i].x = 0.0f; // starting position particle[i].y = 0.0f; // starting position particle[i].z = 0.0f; // starting position for (int j=0; j < steps; j++) { float newz = 2 x randgen() - 1; float alpha = 2 * pi * randgen(); float r = sqrtf(1 - newz * newz); particle[i].x = r*cosf(alpha); particle[i].y = r*sinf(alpha); particle[i].z = newz; if(particle[i].z < 0) {particle[i].z -= particle[i].z;} } }
I used the code to publish several scientific papers regarding electrochemical motion and interaction with surfaces. This is code written by a scientist, rather than a computer scientist with a background in code or programming languages. For lack of a better word, a self-taught noob. I'm a physical chemist first, programmer second.
So one could argue that the loops involved require integers, and the random number generator is predominantly bitshifts, but the bulk of the mathematics that takes time is basic floating point trig functions.
Disclosure: I'm the Senior Editor Ian Cutress on the main site. I don't visit the forums that much(!) If anyone wants to double confirm, I use this handle on Twitter as a secondary account as well as over at OCN. You can tweet me at @IanCutress or @borandi with this link and I'll respond.
Bad compilation with depreciated instructions.So why is this code running so bad on amd's uarch compared to intel's?
Yep, don't use Visual Studio 2008.Is there any optimization a that could be done to take advantage of amd's uarch without advanced extensions?
A new product that didnt exist in roadmaps one month ago, i think that s it s clear that AMD has decided that they ll communicate less than they used to do in the past, just remember Hawai, three months before launch there was no roadmap that talked about this GPU, and i think that there was no roadmap at all that did point it.