And they started so well. Initial idea of their parent project was to replace interpreted stuff with native code where possible and low-level intermediate code where it isn't ( that could be trenslated without much CPU effort). This means that browser would host basically just a VM machine, where it would run the code, natively in most cases.
What it evolved into was just another mix of java/script...
It is absolutely awesome to have when you simply need to run some old program, which is in my case usually bound to some piece of old, but still useful HW, like chip programmer, some old measurement or CNC equipment etc. Or perhaps for analysis of program behaviour in order to do modern reimplementation. Or to enjoy nostalgia trip with some old DOS game...
WRT to FreeDOs development, I don't think it's needed outside integration into modern OS & HW, like having modern drivers for mouse and optical unit, USB useage for printing, nice, antialiased fonts, good high, EMS etc memory manager etc. I/O virtualisation of some sort would be great, so I can, for example have virtual LPT port that would be seen on desired I/O port address and connected to some real LPT port somewhere entirely else or even to USB driver or some userland program through pipe etc.
I don't think susbtantial, grand scale reworks like 32-bit and 64-bit implementation, multicore and multitasking are neccessary. We have plenty other solutions for that.
Well, I don't like Bulldozer, at least not as it is now.
It doesn't make much sense as it is nether here not there. They are trying to sell one modules as two cores, which is ridiculous. Also, it is not clear why in real life one module ( ie by making it execute just one thred with all its resources) can't match performance of one decent core on clock-by-clock basis.
Also, AMD managed to squeeze 6 K-10 cores on 346 mm2 with 45nm geometry on Thuban ( x6 1055,1075,1090,1100T), With 32nm they should be able to use 2x logic on same area. If one module costs them only 18% more die area as the classical core from previous generation, then they should be able to put something like 8-10 MODULES ( and not only 4) on a chip, done with 32nm on 315mm2 like FX-8150. If they went for 350mm2 like before, then even 12 modules, perhaps with a bit less L3 wouldn't be out of the question ( 12 modules = 24 threads ! ).
Users would then get poor man's Magnycores. It would be awesome. And people would understand even if unithread performace sucked - it would be manythreading monster. Even better, they could offer higher clocked versions with just two or 4 modules for those kind of customers. Or even refer them to existing Thubans.
As it is now, it looks as if someone panicked in the late stage of the design and tried to save it by bundling it with shitload of L2 and L3 cache.
CIA had its hands all over Balkan all the time(amongst others) And all that time, there were wery little visible agents that one could point on.
They used various sorts of puppets instead. So, if they're involved in this, those two girls are just getting paid in one way or another and doesn't particularly care or know who is paying them.
After all, why would you need specially trained agent to scream "RAPE!" ?
I use this with all my Epsons and it works beautifully and by far the cheapest.
Refilling the cartridge takes me maybe 2 mins all in all. It's nice to have thin latex gloves if a drop of ink spills, it's kinda hard to wash out from hands and fabric, but that's a minor bump...
I wish Slashdotters would stop with the incessant "x86 sucks" mantra. You're all fools.
There's plenty of crufty old instructions in the x86 ISA; no modern compilers generate them though, so no one cares that they're there. They take up a couple pages in the ISA manual I guess. The die area it takes to implement them is totally, completely insignificant.
Take a look at what it takes to decode x86 instruction in parallel and then we'll talk.
If you can believe USA story that theirs military instructors ( = Blackwater gyus etc) were present in Georgia but only to _DISSUADE_ ( and not, gord forbid, perform instructions and possibly weapons for the attack) Sakashvili from attack idea, then why would you have to be more naive for this story ?
I have several of their motherboards and half of them are on warranty service.
Not only that, they won't be serviced NOR REPLACED, since Foxconn has terminated the model (AM2+ NF570SLI).
And their support sucks royally, right on par with Gigabyte.It's more or less along the line of "you bought the board and can't/won't sue us- so f**k off."
I've just opened official ACPI specs and Microsoft's WHQL is NOWHERE EVEN MENTIONED, let alone of being needed and sufficient criteria of ACPI compliance.
IOW, product is ACI compliant when it works in accordance with specs. Once there is violation found, they can no longer claim ACPI compliance.
I'm long time gentoo user ( I've started around version 1.4) and am more or less stisfied with it. I mean, it definitely has its flaws, but I haven't been able to find substitution that could "scratch my itch".
I have tried Ubuntu as everyone around me were advocating it, but found that while it has much prettier installer and things tend to work out of the box, deep down it's actually inferior to Gentoo. When things work smoothly in Ubuntu, everyone is quick to point out those maybe few minutes and a CLI command that Ubuntu has spared you, but no one mentions those cases when things don't work.
Each distro has its framework which combines many pieces of open source mosaic, but things get interesting when some piece in mosaic develops a flaw that is not immediately obvious or it affects some portion of users. I don't care for a few seconds spared during installation nearly as much I care for infrastructure support in cases that don't work.
WRT to Gentoo's imminent death:
1. If its going to happen, it won't be soon.
2. All problems of Gentoo can be traced to its origins. At the time, its creator found his pleasure in homebrew approach and wanted to have something that works in some way much rather than trying to get it right first time and also answer many organisational, commercial and law questions.
So now we have Gentoo Organisation, Infrastructure and Distro in the state of Russian Orbital station MIR jsut before its death: there are many interleaving and intervening systems with many semi-documented patches and changes and whole shebang is far from original specs. I mean, evolution is a ni ce thing, but it has its limits. When it reaches its limits, maybe its time to use accumulated knowledge and experience to make something new...
3. WRT to Drobbins, I don't know the guy personally and have nothing against him, but I'm not sure that having him back is a good idea. He had the chance but has proven unable to make Gentoo his life, so now he's coming back, faced with similar problems ( needing money for RL but being strawn between his hobby and bussiness) and unable to learn from his mistakes and use radically different solution this time.
4. New Gentoo should start from scratch with its policy, organisation and web/distro infrastructure while good old Gentoo I is living on...
Slashdot Mirror
might drastically improve EV performance in bends...
And they started so well.
Initial idea of their parent project was to replace interpreted stuff with native code where possible and low-level intermediate code where it isn't ( that could be trenslated without much CPU effort).
This means that browser would host basically just a VM machine, where it would run the code, natively in most cases.
What it evolved into was just another mix of java/script...
Who needs that ?
...just for historical reasons.
It is absolutely awesome to have when you simply need to run some old program, which is in my case usually bound to some piece of old, but still useful HW, like chip programmer, some old measurement or CNC equipment etc. Or perhaps for analysis of program behaviour in order to do modern reimplementation. Or to enjoy nostalgia trip with some old DOS game...
WRT to FreeDOs development, I don't think it's needed outside integration into modern OS & HW, like having modern drivers for mouse and optical unit, USB useage for printing, nice, antialiased fonts, good high, EMS etc memory manager etc. I/O virtualisation of some sort would be great, so I can, for example have virtual LPT port that would be seen on desired I/O port address and connected to some real LPT port somewhere entirely else or even to USB driver or some userland program through pipe etc.
I don't think susbtantial, grand scale reworks like 32-bit and 64-bit implementation, multicore and multitasking are neccessary. We have plenty other solutions for that.
So what ?
Many ARMs are sold as unicore 50MHz Cortex 3 for example. Not every application needs 16 cores at 2+GHz, for more than one reason.
And 64 bits is more of an ograde on x86 than other machines especially if one doesn't have more than 3GiB of RAM.
Just curious, what's so wrong with branch with delay slot and isn't that more native way to look at branch ?
Everywhere where it matters ( loops) there is at least one instruction that can be inserted into slot, so this shouldn't be a problem.
Isn't this more problem of compilers that weren't designed to use such feature than architecture's wart ?
It probably can eb hidden within modern implementations, but still it seems nice to have in smallest implementations, possibly on FPGA.
Show me one 20 year old x86 CPU, capable of executing 64-bit code.
And then please explain why would someone with such configuration even go with glibc when there are other, much slimmer choices.
So you will go with small, cheap and economic ARM instead of x86.
Why go for x86 and then worry about a couple bytes of _code_ ?
One can be lover of sport cars and byu a Ferrari. Or one could be a prudent driver and go for Diesel car.
But having Diesel Ferrari doesn't make you prudent performance driver, it makes you a moron.
So, it was meant for the case where you'd go with X86_64, but with anorexic memory ?
Who is so moronic to do that ?
Well, I don't like Bulldozer, at least not as it is now.
It doesn't make much sense as it is nether here not there. They are trying to sell one modules as two cores, which is ridiculous. Also, it is not clear why in real life one module ( ie by making it execute just one thred with all its resources) can't match performance of one decent core on clock-by-clock basis.
Also, AMD managed to squeeze 6 K-10 cores on 346 mm2 with 45nm geometry on Thuban ( x6 1055,1075,1090,1100T), With 32nm they should be able to use 2x logic on same area. If one module costs them only 18% more die area as the classical core from previous generation, then they should be able to put something like 8-10 MODULES ( and not only 4) on a chip, done with 32nm on 315mm2 like FX-8150. If they went for 350mm2 like before, then even 12 modules, perhaps with a bit less L3 wouldn't be out of the question ( 12 modules = 24 threads ! ).
Users would then get poor man's Magnycores. It would be awesome. And people would understand even if unithread performace sucked - it would be manythreading monster. Even better, they could offer higher clocked versions with just two or 4 modules for those kind of customers. Or even refer them to existing Thubans.
As it is now, it looks as if someone panicked in the late stage of the design and tried to save it by bundling it with shitload of L2 and L3 cache.
Affordable. Something like Tyan's dual socket Opteron boards. â300-400.
I second that.
I'm from penguin crowd, but nevertheless it would be really nice to work on some decent, many-cores non-x86-crap design...
Ideally, on dual socket board...
True. Where are all those promised cores ?
Bulldozer was supposed to be about doing things parrallel big time.
All they have shown are four fat cores they call modules, and they paid for each only 18% more transistors than for regular core.
If that is true and if they have 2x bigger transistor budget, shouldn't we be seeing chips with something like 12 modules ?
You are naive.
CIA had its hands all over Balkan all the time(amongst others) And all that time, there were wery little visible agents that one could point on.
They used various sorts of puppets instead. So, if they're involved in this, those two girls are just getting paid in one way or another and doesn't particularly care or know who is paying them.
After all, why would you need specially trained agent to scream "RAPE!" ?
Can you give an example ?
I tried Open64 with bzip2 and result was about the same execution speed as with gcc-4.3 ...
I use this with all my Epsons and it works beautifully and by far the cheapest.
Refilling the cartridge takes me maybe 2 mins all in all.
It's nice to have thin latex gloves if a drop of ink spills, it's kinda hard to wash out from hands and fabric, but that's a minor bump...
I wish Slashdotters would stop with the incessant "x86 sucks" mantra. You're all fools.
There's plenty of crufty old instructions in the x86 ISA; no modern compilers generate them though, so no one cares that they're there. They take up a couple pages in the ISA manual I guess. The die area it takes to implement them is totally, completely insignificant.
Take a look at what it takes to decode x86 instruction in parallel and then we'll talk.
2.95 is/was regarded as a "golden" version for its maturity and stability.
I'm not certain that newest 4.3x is that much better on small embedded system without SSE and FPU units to be worth a swap...
No, UV LEDs are far too costly, fragile and unpolished for this.
Remember how BlueRay still has so many problems because they can not produce UV LEDs to sufficient quantities ?
In fact, many white LEDs use BLUE LED as a foundation, covered with small amount of phosphorus.
Phosphorus then converts some part of incoming blue light to higher wawelentgths and the result is more or less "white"...
...from previous meager 40.something percents to 40.8 current percent.
Scary stuff, man...
If you can believe USA story that theirs military instructors ( = Blackwater gyus etc) were present in Georgia but only to _DISSUADE_ ( and not, gord forbid, perform instructions and possibly weapons for the attack) Sakashvili from attack idea, then why would you have to be more naive for this story ?
This thing is obviously aimed at special applications.
For these kind of things there are much better solutions than x86 chips. They are smaller, faster, cheaper and more economic than classic HW.
Take a look at TI's daVinci program, for example, or maybe some small Coldfire from Freescale or maybe some cool Arm from NXP etcetc.
+1
I have several of their motherboards and half of them are on warranty service.
Not only that, they won't be serviced NOR REPLACED, since Foxconn has terminated the model (AM2+ NF570SLI).
And their support sucks royally, right on par with Gigabyte.It's more or less along the line of "you bought the board and can't/won't sue us- so f**k off."
Yes, but if no one pressures the company, management won't have ANY reason to change cutting corners with half-finished products.
I've just opened official ACPI specs and Microsoft's WHQL is NOWHERE EVEN MENTIONED, let alone of being needed and sufficient criteria of ACPI compliance.
IOW, product is ACI compliant when it works in accordance with specs. Once there is violation found, they can no longer claim ACPI compliance.
I'm long time gentoo user ( I've started around version 1.4) and am more or less stisfied with it. I mean, it definitely has its flaws, but I haven't been able to find substitution that could "scratch my itch".
I have tried Ubuntu as everyone around me were advocating it, but found that while it has much prettier installer and things tend to work out of the box, deep down it's actually inferior to Gentoo.
When things work smoothly in Ubuntu, everyone is quick to point out those maybe few minutes and a CLI command that Ubuntu has spared you, but no one mentions those cases when things don't work.
Each distro has its framework which combines many pieces of open source mosaic, but things get interesting when some piece in mosaic develops a flaw that is not immediately obvious or it affects some portion of users. I don't care for a few seconds spared during installation nearly as much I care for infrastructure support in cases that don't work.
WRT to Gentoo's imminent death:
1. If its going to happen, it won't be soon.
2. All problems of Gentoo can be traced to its origins. At the time, its creator found his pleasure in homebrew approach and wanted to have something that works in some way much rather than trying to get it right first time and also answer many organisational, commercial and law questions.
So now we have Gentoo Organisation, Infrastructure and Distro in the state of Russian Orbital station MIR jsut before its death: there are many interleaving and intervening systems with many semi-documented patches and changes and whole shebang is far from original specs. I mean, evolution is a ni ce thing, but it has its limits. When it reaches its limits, maybe its time to use accumulated knowledge and experience to make something new...
3. WRT to Drobbins, I don't know the guy personally and have nothing against him, but I'm not sure that having him back is a good idea.
He had the chance but has proven unable to make Gentoo his life, so now he's coming back, faced with similar problems ( needing money for RL but being strawn between his hobby and bussiness) and unable to learn from his mistakes and use radically different solution this time.
4. New Gentoo should start from scratch with its policy, organisation and web/distro infrastructure while good old Gentoo I is living on...