watch those 1080p movies on my smart phone screen.
But on a more serious note, Intel will always be able to leverage their advanced fabrication processes to reduce power consumption. Most ARM chips I've seen use older (in terms of desktop CPU) process technology but the good architecture still gives you excellent power consumption.
And there I was thinking it was the credit crunch that has caused our economic problems, it's obvious now that the real problem are the millions of teenage girls downloading britney spears albums (or who ever is in at the moment).
What greatly annoys me is when I see a site has that has for example a "Log On" button but the corresponding button is called "Log Out" when it should be "Log Off".
Sure but that was n't my point, my point was multiple outcomes from the same specification.
Any schmuck writing code is like me getting a copy of AutoCad and drawing up a floor plan. Besides, I've seen many badly designed buildings so being regulated and licensed does n't guarentee good building, it just limits (but does n't eliminate) the possibility of buildings collapsing.
I've always compared software development to architecture in that you can give a specification for a building (size, floors, x rooms, etc) and you can get multiple designs that fit the specification but a great architects design will always stand out.
Sometimes I look at code and it just does n't "feel" right, sure it may work just fine but I may not like the design choices taken whilst sometimes I see code that is designed so well that the peices fit together seemlessly (not that often I'm affraid).
Yes there are women who look more pleasing to the eye after major surgery.
However for me personally when I see the before picture it reduces that persons 'new' attactiveness not because they were 'ugly' before hand but because I get the feeling that the person I'm looking at is n't the 'real' person and to me that is kind of creepy.
Call me paranoid and I have n't read the original Facebook ToS but in terms of privacy what does it guarentee exactly? If you want a conspiracy theory, people are now "happy" going back to the origonal ToS so maybe that was the cunning plan after all.
Although marked as Funny, you could quite easily open the PC take out the BIOS ROM whilst the machine is running (the BIOS is shadowed in normal operation), stick a new custom one in that probes the cache and do a hard reset.
This would be really useful if you wanted to develop a protocol for single long distsance point-to-point linke. I seem to remember Intel was developing something for use in developing countries with a special version of a wireless router but this gives you the source so has much more hack value.
It reminds me of a time when a teacher who was teaching Pascal explained to us that divisions where executed by repeatedly subtracting, sad but true.
The point your teacher was probably trying to make is that not all instructions cost the same CPU time, even if they use the same number of instructions to issue. Depending on when your teacher learned computers, what architecture the class had in mind, and how old his textbook was, his statement might have been true for the cases he was thinking of.
Some early processors (such as original PDP-11) did not have a DIV instruction at first, so Pascal (and other languages) would have had to emulate it. Some embedded processors also do not have a divide instruction. Dividing isn't universal in processor instruction sets. The simplest (although not usually the most efficient) way to emulate a divide is with repeated subtraction. It's also possible for processors that support a divide instruction to internally subtract in a loop. Pascal (and other languages) also had floating point libraries that couldn't rely on the floating point unit being there; it's entirely possible that early versions of those libraries used repeated subtraction.
Anyways, the question that should've come to your mind after that is "how much slower is it?" and then run a timing test of divisions vs subtractions. For example time 1,000,000 loops of (3000-3), and then time 1,000 loops of (3,000/3). If they come out the same, then your division might be using repeated subtraction. Use 3 to avoid the edge cases of anything divided by one is itself, and anything divided by 2 can be bit-shifted.
There are better ways to test, but since Pascal is normally a beginning teaching language this would be a nice simple one that beginning students should think of and be able to do. If the division came out faster, you would have a reason to believe that it wasn't done through repeated subtraction on that CPU and version of Pascal (and libraries). You could then investigate how it was done (there's some fancy tricks depending on the CPU).
This reminds me of a time when a student who was taking Pascal didn't know his computer architecture, sad but true.:)
You give the teacher a lot more credit then they deserve but I can understand if you was trying to make a point about performance divide would be a good example however I seem to recall that this they were n't actually a CS teacher but had "got into" programing at a later date and the class was an introduction to programing.
It was just a passing comment they made that stuck in my mind because the first thing I thougt was how slow that would be where the dividend was large and the divisor small.
How exactly do you think that divisions are implemented ? Even in silicon ? Did you realize that the number of cycle for a DIV instruction is high and dependent on the operand size ?
Ever wondered why the x86 DIV was 14 cycles for 8bits operands, 22 cycles for 16bits and 38 cycles for 32bits ? (hint 6 cycles constant data access + 1 cycle per bit in the subtract/shift loop)
And if the time your teacher told you that was a few years ago, before processor had hardware divide instruction that implemented the loop in silicon, then the pascal run time had to implement division by a series of subtractions and halving...
Now, if he told you that it just subtracted (without halving) then, yeah, he was wrong...
No it was the latter case, ie a loop that kept on subtracting the divisor until 0 or < divisor. The same kind of code talked about here, thats why it came to mind.
Btw, modern x86 processors take less then 1 cycle per bit to division but obviously the algo is the same.
For example I had some code I developed on Windows CE 4.2.NET which kept on hanging on calling the FindWindow() fuction call.
Turns out that trying to find a window by class name will hang (this version of) CE every time, even though you would have thought its a very much used function call and would be caught by CE.
So no I'm not surprised at all that this bug got through.
As a service that the operators could milk their customers with. It was only when it started getting popular that they heard the cha-ching sounds and start charging outrageous fees.
Phones these days have two processors, one which handles the voice/data/etc aspect and an other which has the OS/app/etcs. They have to be seperated since the people that regulate the airwaves mandate that it should be impossible for an app to have access to the RF side of the phone.
Even in OpenMoko this is the case, infact a few pages of the schematic are missing because of TI NDA's so the real sense there are no truely open phones.
Maybe he cares more about the music he's listening to rather than the make/model of the player.
If I did n't have an mp3 player and got a zune for free, as long as it played my mp3s correctly I'd use it. Sometimes I wonder if Apple is a religion or just some company that makes tech products.
I dont know how much money these people are making but having to move locations every two weeks surely is n't free. Plus whilst you're moving and the bot net is down you're not generating money (from the spaming).
If this is the case then I would n't mind this going on for ever until they run out of money.
Maybe the price of the software varies significantly from customer to customer. I mean if you just found out that you paid 2x as much for software mentioned here you'd be pretty annoyed.
watch those 1080p movies on my smart phone screen.
But on a more serious note, Intel will always be able to leverage their advanced fabrication processes to reduce power consumption. Most ARM chips I've seen use older (in terms of desktop CPU) process technology but the good architecture still gives you excellent power consumption.
And there I was thinking it was the credit crunch that has caused our economic problems, it's obvious now that the real problem are the millions of teenage girls downloading britney spears albums (or who ever is in at the moment).
What greatly annoys me is when I see a site has that has for example a "Log On" button but the corresponding button is called "Log Out" when it should be "Log Off".
Sure but that was n't my point, my point was multiple outcomes from the same specification.
Any schmuck writing code is like me getting a copy of AutoCad and drawing up a floor plan. Besides, I've seen many badly designed buildings so being regulated and licensed does n't guarentee good building, it just limits (but does n't eliminate) the possibility of buildings collapsing.
I've always compared software development to architecture in that you can give a specification for a building (size, floors, x rooms, etc) and you can get multiple designs that fit the specification but a great architects design will always stand out.
Sometimes I look at code and it just does n't "feel" right, sure it may work just fine but I may not like the design choices taken whilst sometimes I see code that is designed so well that the peices fit together seemlessly (not that often I'm affraid).
Yes there are women who look more pleasing to the eye after major surgery.
However for me personally when I see the before picture it reduces that persons 'new' attactiveness not because they were 'ugly' before hand but because I get the feeling that the person I'm looking at is n't the 'real' person and to me that is kind of creepy.
Call me paranoid and I have n't read the original Facebook ToS but in terms of privacy what does it guarentee exactly? If you want a conspiracy theory, people are now "happy" going back to the origonal ToS so maybe that was the cunning plan after all.
Additionally this could also be used to get a near perfect dump of RAM too.
Although marked as Funny, you could quite easily open the PC take out the BIOS ROM whilst the machine is running (the BIOS is shadowed in normal operation), stick a new custom one in that probes the cache and do a hard reset.
This would be really useful if you wanted to develop a protocol for single long distsance point-to-point linke. I seem to remember Intel was developing something for use in developing countries with a special version of a wireless router but this gives you the source so has much more hack value.
The point your teacher was probably trying to make is that not all instructions cost the same CPU time, even if they use the same number of instructions to issue. Depending on when your teacher learned computers, what architecture the class had in mind, and how old his textbook was, his statement might have been true for the cases he was thinking of.
Some early processors (such as original PDP-11) did not have a DIV instruction at first, so Pascal (and other languages) would have had to emulate it. Some embedded processors also do not have a divide instruction. Dividing isn't universal in processor instruction sets. The simplest (although not usually the most efficient) way to emulate a divide is with repeated subtraction. It's also possible for processors that support a divide instruction to internally subtract in a loop. Pascal (and other languages) also had floating point libraries that couldn't rely on the floating point unit being there; it's entirely possible that early versions of those libraries used repeated subtraction.
Anyways, the question that should've come to your mind after that is "how much slower is it?" and then run a timing test of divisions vs subtractions. For example time 1,000,000 loops of (3000-3), and then time 1,000 loops of (3,000/3). If they come out the same, then your division might be using repeated subtraction. Use 3 to avoid the edge cases of anything divided by one is itself, and anything divided by 2 can be bit-shifted.
There are better ways to test, but since Pascal is normally a beginning teaching language this would be a nice simple one that beginning students should think of and be able to do. If the division came out faster, you would have a reason to believe that it wasn't done through repeated subtraction on that CPU and version of Pascal (and libraries). You could then investigate how it was done (there's some fancy tricks depending on the CPU).
This reminds me of a time when a student who was taking Pascal didn't know his computer architecture, sad but true. :)
You give the teacher a lot more credit then they deserve but I can understand if you was trying to make a point about performance divide would be a good example however I seem to recall that this they were n't actually a CS teacher but had "got into" programing at a later date and the class was an introduction to programing.
It was just a passing comment they made that stuck in my mind because the first thing I thougt was how slow that would be where the dividend was large and the divisor small.
How exactly do you think that divisions are implemented ? Even in silicon ? Did you realize that the number of cycle for a DIV instruction is high and dependent on the operand size ?
Ever wondered why the x86 DIV was 14 cycles for 8bits operands, 22 cycles for 16bits and 38 cycles for 32bits ? (hint 6 cycles constant data access + 1 cycle per bit in the subtract/shift loop)
And if the time your teacher told you that was a few years ago, before processor had hardware divide instruction that implemented the loop in silicon, then the pascal run time had to implement division by a series of subtractions and halving...
Now, if he told you that it just subtracted (without halving) then, yeah, he was wrong...
No it was the latter case, ie a loop that kept on subtracting the divisor until 0 or < divisor. The same kind of code talked about here, thats why it came to mind.
Btw, modern x86 processors take less then 1 cycle per bit to division but obviously the algo is the same.
Or used hardware from another manufacturer.
Na that would be silly as it would require a basic understand of math.
It reminds me of a time when a teacher who was teaching Pascal explained to us that divisions where executed by repeatedly subtracting, sad but true.
For example I had some code I developed on Windows CE 4.2 .NET which kept on hanging on calling the FindWindow() fuction call.
Turns out that trying to find a window by class name will hang (this version of) CE every time, even though you would have thought its a very much used function call and would be caught by CE.
So no I'm not surprised at all that this bug got through.
As a service that the operators could milk their customers with. It was only when it started getting popular that they heard the cha-ching sounds and start charging outrageous fees.
Phones these days have two processors, one which handles the voice/data/etc aspect and an other which has the OS/app/etcs. They have to be seperated since the people that regulate the airwaves mandate that it should be impossible for an app to have access to the RF side of the phone.
Even in OpenMoko this is the case, infact a few pages of the schematic are missing because of TI NDA's so the real sense there are no truely open phones.
and twice at that :D
If it was ever to be the case where polygamy became the norm because of the lack of males, nothing would change!
Womens selection criteria would still be the same except that now men who had previously been unaviable are avialable.
If anything this reduces your chances.
Maybe he cares more about the music he's listening to rather than the make/model of the player.
If I did n't have an mp3 player and got a zune for free, as long as it played my mp3s correctly I'd use it. Sometimes I wonder if Apple is a religion or just some company that makes tech products.
It's not perl if its not nearly completely unreadble :D
I dont know how much money these people are making but having to move locations every two weeks surely is n't free. Plus whilst you're moving and the bot net is down you're not generating money (from the spaming).
If this is the case then I would n't mind this going on for ever until they run out of money.
Maybe the price of the software varies significantly from customer to customer. I mean if you just found out that you paid 2x as much for software mentioned here you'd be pretty annoyed.
Plus there is always corporate paranoia..
For people who don't know, this is reference to an episode of Red Dwarf (Back to Reality, season 4 ep 6).
Growing things in pots is a transgression in Michigan?