Comment Re:Oh bullshit! (Score 1) 320
Yup. Sarcasm mode was enabled during that post.
Yup. Sarcasm mode was enabled during that post.
Music for your pillow waifu.
More like music to go with my otokoyama.
I like Tokyo Jihen, Happy Day, Kicell, Yukawa Shione, Predawn and a few others.
I've taken to coding with Japanese music. I don't have a clue what they're singing, so they don't interfere with the language processing in my brain.
>Talk to the people at Intel and ARM who know about this
I am one of those people.
WTF does "settled charges" mean? Who went to jail? Who was prosecuted? Where and when was the court case?
I knew the patent system was horribly broken but this is obscene. Perhaps I'll patent "Utilizing a multi-wheeled conveyance to traverse a network of engineered level surfaces to traverse from an origination point to a destination point". This patent doesn't seem to cover any real technology but the general idea of "launching from a land site and landing on an ocean platform".
It's rather like "Do X, but on the internet" patents. However it's "Do X, but at sea on a platform"
there is a linear relationship between code density and the functional bandwidth of the instruction caching at every level.
Even if this were true (which it isn't), and even if you were right that CISC has twice the code density of RISC (which it doesn't), it would still be a long way short of proving your claim that CISC gives better performance than RISC.
I don't presume to understand why ARM do what they do.
Certainly not 2X, that was normal slashdot hyperbole. 1.2-1.5X depending on what you compare with. But you are putting words in my mouth. Nowhere did I claim RISC was better than CISC or visa versa in any general sense. I said that compact instruction encodings are better than inefficient instructions encodings, which they clearly are for a broad class of CPU memory hierarchies that have been around in recent years. The decoding benefits of RISC were tangible for 1990 era CPUs, but the decoding overhead hasn't changed, while the rest of the CPU has got much bigger. So the decoding overhead is now negligible for the CPUs we put in phones and PCs, while the instruction bandwidth has a bottom line effect on performance. You can address it with wider buses and bigger caches, but then you can have wider buses and bigger caches with smaller instructions too.
I'm not seeking to prove a claim. It's just the way things are.
Accordingly a CPU with a real Huffman coded instruction set might be even better. Feel free to go implement one.
I don't need to presume, I know that they removed some complex instructions because they made the hardware more complex and reduced performance.
Which contradicts the evidence of the vast majority of CPUs ever made, which is they get faster as you throw more gates at them.
That puts me in the 2%. Is that good?
N machines where N > 2.
As long as N > 2, the problem is unchanged for any value of N.
It's too many words to fit on a Marquee, and takes too long to say to the ticket vendor. By the time you say "One for The Man who went up a hill and came down a Mountain", the ticket agent has already given you your ticket, change, and is halfway through serving the next person in line.
But I did actually see that film. Making life easy for the marquee layout is clearly not the same thing as making money.
Yes, but now that '50 Shades of Grey' is out, can you imagine what the producers would have wanted to do with a title like that?
How about : "Pantone PMS 400-447 and a Couple More"
I remember an interview from years back where she was asked if she used email and her response was along the lines of " Oh no. Emails are discoverable".
So yes, she knew exactly what she was doing and why she was doing it.
Emails are discoverable whether you use a public or a private email address.
Yes. That's what makes the current news interesting. She wasn't hiding them. She handed them over in response to a request. She wasn't not-allowed to use personal email. The rules had no such restriction. But her actions conflict with what I remember her saying was motivating her to not use email.
I keep seeing people declare TLS's cipher choices to be mess and propose cleaning them up somehome. Look deeper. The problem is not adding things, it is retiring things. If you can't retire algorithms, you can't clean up. If you can't clean up, then negotiation is bad.
So you have to live with your initial choices. Make them well.
I suspect I'm much more likely to go and watch a film called "The Moon is a Harsh Mistress" than one called "Uprising".
He has not acquired a fortune; the fortune has acquired him. -- Bion
