"Huge losses & "breakeven" in the next year or two in the mobile sector is not something to hang your hat on."
The accounting of charges is difficult to allocate to specific divisions. For example, the Silvermont core they developed is being used in both PC client products and in Knights Landing. Features are also being incorporated into the lower power server chips. Intel does not adjust the accounting for cross division sharing of IP. Much, if not all, of the development would have been done anyway.
"No sense of urgency among the workforce. "
Just curious. How many of the work force did you survey?
"Server growth (mainly by IaaS cloud providers) is literally the only growth area that is making an impact"
... and will likely continue to do will by borrowing the mobile IP and incorporating it into the server products.
It appears to me like Intel has almost skipped the Broadwell designs and going directly to Skylake. It doesn't make sense to me if it is just incrementally better graphics and power ... which is what I (and most people) think.
It has to be more dramatic than just the next version of power reduction and graphics performance.
Wireless charging is a system design issue .... isn't it? My daughter damaged her Samsung charging connector and added wireless charging (simple adapter placed inside on battery and an external plate) for $20-$30 to postpone buying a replacement phone. I doubt she will go back to cables unless she has to.
I think the HTC cheat was to insert some scripts to recognize when a benchmark was running and then boosting the operating behavior of the device to enter high power mode best for benchmark numbers. If you changed the name of the benchmark program, it would run at normal speed.
I think that Samsung did the same thing as HTC.
"Well, for a start AVX2 isn't supported in silvermont:) But, I know where you are coming from. "
AVX2 does not need to be supported in order for Silvermont code to benefit. When ICC is opened up for AVX2 work, the new algorithms are incorporated throughout the compiler and all the code generated benefits from the new work. The point is that a huge amount of energy was invested in parallel/vector work. The compiler code analysis starts at the common front end and splits at the code generator.
If you continue to read that thread you quoted, more testing was done by Nothingness and his conclusion "I know some will still deny, but all my doubts have vanished: icc is definitely cheating." .
... and after a little discussion, he backed off a little "On my side I'm 99.9% confident Intel cheated.". He was upset and venting.
"Sentiment: Strong Buy"
Did your "sentiment" change or did you just get sloppy?
" It has been over a month since that has happened."
Did you just make a mistake or is your "analysis" just getting sloppy? The MARKET has NOT been up 2 days in a row but Intel has. The market, as measured by SPY, has not been up 2 days in a row during the last month. Intel, however, was up 3 days in a row on March 2, 3 and 4. Intel managed these 3 UP days in the month following ex-dividend when INTC is traditionally weak.
"Does that really represent your position?"
More or less.
The article contains much good information and analysis. The author confesses his ignorance about legitimate examples and then makes some assumptions based on that ignorance. I am personally aware of examples that he is not. The author points out that the optimization is a new optimization and that is true. It was inserted to support the 256-bit AVX2 integer operations in Haswell silicon and the upcoming AVX512 instruction set. He just arrives at incorrect conclusions based on his not being aware of the practical application examples. I arrive at different conclusions based on my personal knowledge.
"but this isn't what happened...ICC broke the benchmark - nothing to do with vectorization of code."
Seems like what the compiler did was something called an "automatic vector transformation" where the compiler transformed a program loop operating on 1-bit data into a program loop that operated on 32 data elements on each loop. The ICC compiler would generate AVX2 code to transform the same loop operating on a 1-byte character array into a loop operating on 32-bytes each iteration. Can you explain why that logic is wrong?
"The question becomes is GB a good proxy or not?"
Agree. Then the discussion becomes: What is a collection of GB over weighted compression/decompression, encryption/decryption benchmarks a good proxy for?
My concern is that GB contains a pile of code fragments that get far more respect than they deserve.
Ugh! The rubout key kills the Yahoo screen and my message ..... the space bar posts partial messages.
I re-read the AnandTech 7-10-2013 Exophase "AnTuTu and Intel" forum posting and it seems represent my position.
I raise VECTOR because the Intel compiler has undergone major work to improve vectorization driven by customer code, new instruction support and ... not some desire to "cheat" on AnTuTu.. The result of this work was a compiler that is better at identifying and generating parallel code.
The ToggleBitRun() function operates on a bitmap (vector) and sets/resets a section of that bit vector.
As for "CPU benchmarks", I think they are not very valuable. For me, a benchmark is a proxy for how my workload will perform. Which one of the benchmarks is a proxy for "voice recognition" since that is important to me. General CPU benchmarks tell which runs that particular code faster/slower but ... that has limited value.
" The real issue was was ICC applying optimizations that only worked for AnTuTu (and no other application). "
This is simply not true.
The ICC vector optimization effort was driven by development of in-memory, column oriented databases and HPC apps. The ICC vector optimizations track the releases of the SAP HANA and Oracle in-memory databases (Times Ten) which use dictionary driven, column structures. You get stunning performance improvements in decision support queries. AnTuTu likely had no part and was a surprise to Intel.
TSX for OLTP and Vector operations database DSS operations.
"The point of having these cryptography sub tests (along with compression tests) is that they are very good at representing general integer cpu performance."
If you want to think so. That is fine with me. Like I said ... we simply disagree. If that were the goal, then it was really dumb for geekbench to select code that distills a loop down to a single instruction. It should give you an indication of how little thought they gave to the design of their collection code 1990's code fragments. AnTuTu too.
"No, the issue was that ICC was removing loops from the benchmark. This "optimization" was specific to Antutu."
If you are saying that the optimization was generated only for AnTuTu, then this is where you and I ... I guess disagree.
It would be silly to think that Intel's focus on vector code generation improvements for HPC, AVX, AVX2, AVX512 was not going to cause optimizations to percolate down the entire complier. AnTuTu was broken and the dead code was bound to be eliminated.
Besides .... "it's easy enough to strip the score from the number" from the AnTuTu results. 8-).
Geekbench 3.0 .... who on earth uses a SHA application during anything that they do? What % of time they use their device would that represent?
IMO, 0% use SHA and it represents 0% of real work unless SHA is built into some app I am not aware of.
"Antutu, the benchmark that Intel cheated in? Once a cheater...:)"
The Intel compiler broke the AnTuTu benchmark and AnTuTu "fixed" it so the code could not be auto-vectorized. End users will benefit from the ICC vector optimizations even if the benchmarks do not show it. When a compiler breaks a benchmark, that is "good".
That is quite different than geekbench 3.0 which intentionally chose benchmarks (SHA1/SHA2) that explicitly give an edge to native instructions.
You are both right but are talking about different things. During the limited construction time, there will be the construction jobs and related support industry jobs created in eastern Montana, South Dakota and Nebraska. There will be a much smaller number of permanent jobs created for the long term care and feeding of the pipe. These states already have the lowest unemployment rates (below 3%) and would require more people relocate into already stressed areas without housing and infrastructure in place. One reason for the high wages will be the extraordinary high cost of living in those areas.
The project supplements an already existing 30-inch pipeline with a 36-inch pipeline BUT the key difference is that the pipeline will be routed to pick up oil from the eastern Montana & Dakota Bakkan formation.
IMO, it has less to do with Canadian tar sands than it does with Montana oil companies looking for curbside pickup of their oil. I would just prefer more transparency large projects like this. The Nebraska, Dakota and Montana farmers and ranchers who own the land to be crossed are not pleased about it.
They cut the target from $40 to $38. Not $30.
INTEL CORP: CANACCORD GENUITY RAISES TO BUY FROM HOLD; CUTS TARGET PRICE TO $38 FROM $40
Is there a CPU in the Intel 7360 modem?
What kind do you think it would be .... since Intel is one of ARMH largest customers?
"I don't see how INTC is even up today"
I think your error is assuming that Intel was priced at "THE CORRECT" market cap. The market change today indicates that market cap assumption may be low.
It looks like there is a number of option series with very high volumes.
29,000 call contracts 3/20 exp $35 are being sold so they appear to think "below $35 for next Friday"
11k call/put contracts on several series between $33 and $35.
They appear to define the expected range through earnings.
Why do you keep bumping this backbay_bstn thread up?
It was dead shortly after he posted it.
You bumped up yesterday and then a couple times again today.
There is a good possibility that a serial-bumper is also the original author.
Could also be related to the Facebook announcement that they are going to use the Intel Xeon D-1540 for their server farms. It appears that the Facebook and Intel have been working for together on this design.
So you are WW's "Lucy". I thought your message sounded familiar.
Can Intel Squeeze a Dime Out of Today's Rally?
by lucifer_nuff • Aug 23, 2011 10:36 AM Flag
The Magic 8-Ball sez "DON'T COUNT ON IT"
Can Intel Squeeze a Dime Out of This Rally?
by lucy_nuff • Aug 22, 2011 1:57 PM Flag
The Magic 8-Ball says "It's questionable."
"hysteria from this liberal 'green' consensus "
.... and we can then examine the issue from the "other side" funded by the carbon industry (correct?). The "consensus" group however is slight larger than the "liberal green" advocates. It would be silly to think that 97% of those with an opinion are "just the green".
"after nearly 200 years of industrialization and the doubling of air CO2"
I would think the "doubling of air CO2" happened in a much narrower time frame .... probably defined by world wide crude oil and coal production. If you examine production curves, they both ramp up in mid-to-late 20th century. Oil production ramps in the 1950's and 1960's .... automobile. Coal production spiked once around 1900 (power plants) and again in 1970's and 1980's.
At that same time, wide spread deforestation eliminated the trees and vegetation that consumed the CO2 and generated O2. CO2 generators multiplied. CO2 consumers were eliminated.
The first 150 years of industrialization can probably be ignored and the impact generated from the last 60 years.
"none of which has seriously affected anyone on Earth and stop being brainwashed by this AGW movement which is primarily politically and economically motivated by non-carbon energy industries."
There are some Pacific Islanders who have abandoned their islands and bought a chunk of land in Fiji who would disagree and say they are "someone".
What is really amazing is the failure of the existing carbon industries to detect and stop this widespread brainwashing of 97% of the scientists. How can those behind these tiny solar and wind energy companies be so successful at their brainwashing? These solar industry groups must have some terrific brainwashers.