Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×

Comment We're no longer at the origin (Score 1) 181

Architectural improvements for general purpose CPUs yield less and less benefits: Even more registers? Even better branch prediction? Even larger caches? It'll all yield but a few percent, at least for current Intel designs. So, the way to go is currently more and more cores, but what good is it to have many cores that can't all fire simultaneously?

Comment Clickbait Caption, but Valid Arguments (Score 3, Insightful) 181

Of course general purpose CPUs exist, simply because we call them that way. But it is also true that each design has it's own strengths, and "dark silicon" is another driver for special purpose hardware. Efficiency is another. Andrew Chien has published some interesting research on this subject. In his 10x10 approach he suggests to use 10 different types of domain-specific compute units (e.g. for n-body, graphics, tree-walking...), each of which is 10x more efficient than "general purpose CPUs" in its domain (YMMV). Those compute units bundled together, make up one core of the 10x10 design. Multiple cores can be connected via a NoC.

Let's see how software will cope with this development...

ps: can special purpose hardware exist if general purpose hardware doesn't?

Power

Denmark Plans To Be Coal-Free In 10 Years 332

merbs writes "Earlier this year, Denmark's leadership announced that the nation would run entirely on renewable power by 2050. Wind, solar, and biomass would be ramped up while coal and gas are phased out. Now Denmark has gone even further, and plans to end coal by 2025.

Comment Re:And so therefor it follows and I quote (Score 1) 353

Why didn't you just order a hamburger?

Because nobody offers that option. I would gladly request a refund for the Windows 7 that came with my notebook if I could. The only reason I keep its partition is because I paid for that crap, and just "in case I need it"... but it's been 3 years so far without booting it. I guess I'll just wipe it and give more space to my Linux partition whenever I get some time to do it.

Comment Re:Hai! (Score 1) 111

One reason might be that railways are more efficient in densely populated areas. There express trains can even compete with airplanes. Yesterday we went from Tokyo to Osaka. Flight time would have been ~1h, plus 1h checkin and transfer to/from the airport (~45min. each). The Nozomi Shinkansen took us there in 2:30, and both stations were directly at the center of the cities.

Most of Japan's population is situated in coastal regions, so just a hand full of routes can service all major cities. Imagine how many connections you'd need in the US...

Comment Re:bitcoin (Score 1) 241

Double spends for anyone who can connect to both sides of the network. Essentially, there will be two ledgers, an International ledger and a Russian one. If you spend on the Russian ledger, the International ledger will still have your money. When the network rejoins, whatever ledger has the most hashing power behind it will be chosen as the correct one, and all the transactions from the other one will be retried on the new global ledger. If the network saw a new transaction spending a previous transaction's outputs, it would be rejected, as well as any spends referencing that transaction, and so on.

Thank you, that's exactly what I wanted to know.

This happened already.

I guess I've missed the news, any links for my lazy ass?

Bitcoin sounds like a nice investment for dictators willing to further screw their populaces.

Comment Re:Still... (Score 1) 193

E.g., would you rather try to see which bit is set in a string like "0b001011010011011101011100" or have it broken up like "0b0010_1101_0011_0111_0101_1100" or "0b00101101_00110111_01011100". If it's a bit field, you may even want "0b001011_010011011_01_0_111_0_0" if breaking it into fields has meaning.

Such a small change to help readability...

If you're really interested in readability you would probably define those bits, like:

#define HIGHSTUFF (0b001011 << 17)
#define NOTSOHIGHSTUFF (0b010011011 << 8)

and then or them together.

Alternatively you could define a macro for your bit field, like:

#include
#define bitfield(a,b,c,d) 0x##a##b##c##d
int main() {
        printf("%x", bitfield(f,f,f,f));
}

Slashdot Top Deals

"Ninety percent of baseball is half mental." -- Yogi Berra

Working...