Quite possibly that might have something to do with the fact that linux is executing a HLT when it is idle, while windows goes into an endless loop. Since your computer likely spends most of its time being idle, it doesn't generate much heat compared to when Tom runs windows.
frames per second: can anyone tell the difference between 60 and 70 frames per second?
high average FPS implies high LOWEST fps
colors: anything above 4096 cannot be discerned
try a gradient
Re:Treat r0 more like /dev/zero
on
Itanium Update
·
· Score: 1
These examples just requires that you can read r0, and get zeroes from it, right? That is present in IA64 and useful and nice, as you clearly demonstrate.
I think it was just writing to r0 that wasn't allowed, and I can't figure out why anybody would want to do that.
Besides, if there had indeed been different code generated, that'd be a typical example of a situation in which you should fix it in the compiler, NOT in the code.
It's interesting that a write to R0 is defined to fault. Is this just for Itanium or is it an IA64 architectural decision? If so, it seems like a very poor one to me.
Why, except perhaps that it seems a bit like wasted effort to check for accesses. Why would you want a/dev/null in asm?
or, since what kernel you run really quite likely doesn't matter (somebody COULD have your 2.4.x-kernel during the night and rebooted everything on FreeBSD, and you wouldn't notice anything now sitting in X using mozilla) perhaps just say you run 'unix', says what needs to be said but the religious nuts might be unhappy about it. Or name the part that matters: I run gnome or I run kde.
Not including the GUI seems a bit harsh. No, I can't come up with a good definition of what constitutes the OS either. A good start I'd say would be to include all parts into which essentially all applications on make system calls, or couldn't live without. So if you never use X, your definition might qualify. For everybody else, it's flamebait:). It's like saying windows 95 is not a OS but just a graphical shell above DOS - it obviously is an OS, thoguh a bad one.
WHY don't these guys just start finishing the HURD then? That way, they could have their own system, and call that GNU. Everybody else would get a different kernel to choose from.
However, in the next few decades the situation might be changing with the planned projects that could actually be able to give us glimpses of the other worlds.
Could you please tell more about what projects are planned that might reveal more about those exoplanets?
I don't have the docs available right here now, but I'd dare guess that this seemingly pointless duplicate function was introduced to facilitate easy maintenance of both unicode and non-unicode versions of the same program.
MS has been trying to get developers to start using unicode for quite some time, and nt/w2k is for example using unicode the full way. All relevant (string-using) function calls in libraries have two versions, one unicode (with a W suffix) and one non-unicode (a 'A' suffix) that converts the passed string to unicode, and then calls the unicode version.
Anyway, to avoid having to change anything in a program to get a unicode version, MS has introduced macros for all relevant data types and function calls. By changing a #define before you include the windows headers, you select which functions you want to link in and how the data types should be declared. If you want to go the unicode way, a function such as StrCpy() would be #defined as StrCpyW(), while if you didn't specify the unicode define, it would be StrCpyA(). This way, if you have used these functions calls and the relevant data types consistently, getting a unicode version is just a #define and a compile away.
yeah, 'dope it with Fe', a energy figure taken from the sky, and 'how about the millions of people working in the power industry'.... Man, WHAT a troll! I'm surprised it went through. Notice the statement about hydrogen bomb - it was perfectly trollish! Some people will invariably try correcting it, saying that hydrogen bombs use fusion, and others will point out that he correctly said fission _powers_ (starts) the fusion.
eh... something is seriously wrong with that font. It looks truly ugly. I thought KDE antialiasing used FreeType's renderer? It is a LOT better than that? What has happened??
while I admittedly didn't initialize p (not that it really matters), I did make sure you couldn't miss this important moment with almost a whole second!:) and don't forget to ntpdate some servers you _REALLY_ trust!:))
Of course, since you are smart enough not to run unknown binaries in unix as root, you are also smart enough to not run windows binaries as administrator, and thus this problem goes away.
That would be a solution yes. I don't like it - if for no other reason, the syntax highlighting doesn't show me what parts were 'commented out'. For that reason, if it isn't too much code, I'd rather enjoy the pain of having to change the comments, constantly cursing the author.:(
(vaguely related: damn I wish somebody would "back port" the "//" comment notation from C++ to C. So much quicker to type for those quick one-liners to explain a small point...)
Not to mention that it makes it A LOT easier to comment out a few lines of code - you surrond the lines to comment out with/* and */, and it works EVEN if there are comments (of the// type) inside the block. This is a thing that really makes me hate people who use/* */ as comment inside the code. Oh, and vaguely related: People who in C++ insist on not defining the loop variable inside the for() statement, when it isn't used anywhere except in the loop (or not at all except as a counter). Scenario: Have several of these for loops (unnested) in a function. Comment out around the first one. Now the second one doesn't have the counter variable defined. Hate it. Oh well..
Slashdot Mirror
haha! Couldn't you please scan that stub and put it on the net, along with the story?
Quite possibly that might have something to do with the fact that linux is executing a HLT when it is idle, while windows goes into an endless loop. Since your computer likely spends most of its time being idle, it doesn't generate much heat compared to when Tom runs windows.
frames per second: can anyone tell the difference between 60 and 70 frames per second?
high average FPS implies high LOWEST fps
colors: anything above 4096 cannot be discerned
try a gradient
These examples just requires that you can read r0, and get zeroes from it, right? That is present in IA64 and useful and nice, as you clearly demonstrate.
I think it was just writing to r0 that wasn't allowed, and I can't figure out why anybody would want to do that.
Besides, if there had indeed been different code generated, that'd be a typical example of a situation in which you should fix it in the compiler, NOT in the code.
It's interesting that a write to R0 is defined to fault. Is this just for Itanium or is it an IA64 architectural decision? If so, it seems like a very poor one to me.
/dev/null in asm?
Why, except perhaps that it seems a bit like wasted effort to check for accesses. Why would you want a
or, since what kernel you run really quite likely doesn't matter (somebody COULD have your 2.4.x-kernel during the night and rebooted everything on FreeBSD, and you wouldn't notice anything now sitting in X using mozilla) perhaps just say you run 'unix', says what needs to be said but the religious nuts might be unhappy about it. Or name the part that matters: I run gnome or I run kde.
Not including the GUI seems a bit harsh. No, I can't come up with a good definition of what constitutes the OS either. A good start I'd say would be to include all parts into which essentially all applications on make system calls, or couldn't live without. So if you never use X, your definition might qualify. For everybody else, it's flamebait :). It's like saying windows 95 is not a OS but just a graphical shell above DOS - it obviously is an OS, thoguh a bad one.
WHY don't these guys just start finishing the HURD then? That way, they could have their own system, and call that GNU. Everybody else would get a different kernel to choose from.
I fully agree with you. People buying something like winzip for $25 is.. well... absurd... annoying...
:)
However, end of moneky business soon comes: WinXP includes zip support!
However, in the next few decades the situation might be changing with the planned projects that could actually be able to give us glimpses of the other worlds.
Could you please tell more about what projects are planned that might reveal more about those exoplanets?
I don't have the docs available right here now, but I'd dare guess that this seemingly pointless duplicate function was introduced to facilitate easy maintenance of both unicode and non-unicode versions of the same program.
:)
MS has been trying to get developers to start using unicode for quite some time, and nt/w2k is for example using unicode the full way. All relevant (string-using) function calls in libraries have two versions, one unicode (with a W suffix) and one non-unicode (a 'A' suffix) that converts the passed string to unicode, and then calls the unicode version.
Anyway, to avoid having to change anything in a program to get a unicode version, MS has introduced macros for all relevant data types and function calls. By changing a #define before you include the windows headers, you select which functions you want to link in and how the data types should be declared. If you want to go the unicode way, a function such as StrCpy() would be #defined as StrCpyW(), while if you didn't specify the unicode define, it would be StrCpyA(). This way, if you have used these functions calls and the relevant data types consistently, getting a unicode version is just a #define and a compile away.
So no plot nor hidden agenda:
Go buy a Silverado and improve your Quality-of-Sleep.
You seem to quite a lot about this. Could you please tell more about how radiometric dating is used to estimate the age of earth?
glass is a liquid (albeit an extremely viscous one). Over time, it pours
No, it doesn't.
yeah, 'dope it with Fe', a energy figure taken from the sky, and 'how about the millions of people working in the power industry'.... Man, WHAT a troll! I'm surprised it went through. Notice the statement about hydrogen bomb - it was perfectly trollish! Some people will invariably try correcting it, saying that hydrogen bombs use fusion, and others will point out that he correctly said fission _powers_ (starts) the fusion.
with that subject, I'd not have opened it anyway - it's obvious spam.
eh... something is seriously wrong with that font. It looks truly ugly. I thought KDE antialiasing used FreeType's renderer? It is a LOT better than that? What has happened??
while I admittedly didn't initialize p (not that it really matters), I did make sure you couldn't miss this important moment with almost a whole second! :) :))
and don't forget to ntpdate some servers you _REALLY_ trust!
int main()
{
int p;
while (1) {
usleep(100 * 1000);
if (p != time(0))
printf("tid: %d\n",time(0));
p=time(0);
}
return 0;
}
Who's ESR?
yes, and if you don't run as root in unix you're likely to know you shouldn't do so in NT, either.
Of course, since you are smart enough not to run unknown binaries in unix as root, you are also smart enough to not run windows binaries as administrator, and thus this problem goes away.
That would be a solution yes. I don't like it - if for no other reason, the syntax highlighting doesn't show me what parts were 'commented out'. For that reason, if it isn't too much code, I'd rather enjoy the pain of having to change the comments, constantly cursing the author. :(
(vaguely related: damn I wish somebody would "back port" the "//" comment notation from C++ to C. So much quicker to type for those quick one-liners to explain a small point...)
/* and */, and it works EVEN if there are comments (of the // type) inside the block. This is a thing that really makes me hate people who use /* */ as comment inside the code.
Not to mention that it makes it A LOT easier to comment out a few lines of code - you surrond the lines to comment out with
Oh, and vaguely related: People who in C++ insist on not defining the loop variable inside the for() statement, when it isn't used anywhere except in the loop (or not at all except as a counter). Scenario: Have several of these for loops (unnested) in a function. Comment out around the first one. Now the second one doesn't have the counter variable defined. Hate it. Oh well..