You are seriously posting that question on slashdot? Open source means anything to you? That's the big one. And then there is the advantage of having an alternative to x86 and ARM that is widely supported, extensible and without license and patent (?) fees.
It can be reduced but AFAIK not be eliminated. Acrylamide is created in the roasting process.
And the blurb is wrong - acrylamide have been reduced in chips but not eliminated. This by improving the processing, controlling temperatures better etc.
You don't understand that by letting Ecuador get away with their childish game there may be more severe consequences than letting one of your "actual British bail jumpers" (Assange is one too FFS) walk free for a few more days. And it's much easier to keep watch when the location of the wanted person is known. Should they just let it slide by?
Discrimination in itself is allowed, only discrimination of a number of protected groups aren't. IOW "no shirt no service" is okay, "no n*ggers" isn't.
Because this is about criticism for a apparently stupid decision from a company with near-monopoly power for a certain market subset, not (as far as I've seen) claims of illegal censorship...
Just because you are anonymous you don't have to act stupid.
Yes but the mess is due to its longevity! Remember we are talking about an architecture released in the 70's and now being 40 years old.
Core instructions aren't outdated with a few exceptions (when designing AMD64 some old instructions were removed and some reused), some instructions aren't used much anymore but are similar and execute in the same execution units as new extensions, some are just supported but not optimized for.
Compare with the original ARM instruction set which was released later but have had more incompatible extensions (reusing the same instruction encoding) and even a very incompatible change to extend the address space.
I don't claim it's a beautiful design or that there aren't better ones just that it isn't too bad.
--
The main problem with x86 isn't decoding but finding the start/end of internal fields.
[0-x prefixes] [op] [R/M] [SIB] [disp] [imm]
([op] can also be a [0xf] [op] in processors after the 8086/8088 for extended instructions)
You are wrong. Dark matter and dark energy are used as they are the only things that help explain our observations of nature.
Yes our theories are still wrong. They will be until we can describe everything - something not likely to ever happen. That's science. What you are doing is hand waving without understanding the basics.
Bullshit. He isn't important, he isn't dangerous and he doesn't know anything. If he suddenly vanished the US would be blamed and that would be a greater price to pay than the value of having an unimportant egocentric bitch under control.
Did you remember to look up in the sky for black helicopters before posting?
X86 isn't that bad. It's easier to decode than many other architectures, it's easier to make superscalar than many others, it support extensions of the instruction set. The last one is why we are still using x86.
X86 processors execute x86 instructions. They are x86 and only a subset of instructions aren't executed directly. There is no translation hardware unless you call the instruction decoding translation (technically correct) and then almost every processor made have/had translation hardware. Instruction fusion? Used on RISC. Instruction splitting? Used on RISC. Detection of special cases? Used on RISC (e.g. r0 or r31 defined as zero). Those are all optimization tricks.
Need to have access: Internet or any other network will do. No need for physical access. Able to execute arbitrary code: many ways to do that.
Do you realize that Meltdown and the other Spectre exploits that made everyone rush to patch operating systems and user software require both access to a system and the ability to execute arbitrary code? In fact this looks like a variant of the Spectre family using another type of branch predictor manipulation.
can be exploited by an attacker to obtain potentially sensitive information
In other words, there is a one in a billion chance that an attacker would obtain something of importance.
Not in the given citation. Potentially means potentially, nothing more, nothing less.
The attacker needs to have access to the targeted system and they must be able to execute arbitrary code
In other words, a completely worthless exploit.
Getting arbitrary user code running is relatively easy and any exploit that can bypass any kind of protection from a user mode program is a real problem.
Well current solutions do use raster graphics - but I'd be very surprised if realtime raytracing didn't use it too. Representation -> Renderer -> Framebuffer -> Screen. You are of course right about the misuse of the term.
There have been at least one polygon renderer that didn't use a framebuffer (don't remember the name/company) but with severe limitations: for every rendered pixel a hit test had to be done with every polygon which strongly reduced the numbers of renderable polygons. Add the problem of "racing the beam" and even with pipelining polygons had to be stored in expensive SRAM memory as variable latency couldn't be hidden. I'd prefer a framebuffer.
No those that know the stuff pointed out the problems with such types of engines, a kind that was known and tried but not used as polygon engines were simply put superior. Sampling artifacts, memory use, inflexibility due to extensive pre-processing...
Early demonstrations of the engine show some limitations (even though demonstrations tend to hide problems as much as possible), repeated objects aligned the same way to decrease memory needs, no moving sprites etc. Later demonstrations showed sprite type objects but with limitations (IIRC axis aligned only), more variation in models etc. but then computers were faster and had more memory. Later still I saw it was to be used as a point cloud renderer, possibly the best use of something like that.
But again the problems with such rendering techniques are well known, it isn't used as it isn't good for most things.
While the music industry should be punished for blatantly lying about damages I don't have any sympathy for this individual assuming he earned money or other compensation for running this operation.
Jury nullification is a tool not to be used lightly - otherwise mob justice is the result.
Need: target shoots, hunts. Personal protection isn't part of a need - if there is a persistent need for protection it will be provided by the state. Some exceptions apply.
People prone to violence or have another condition that can make them hurt themselves or others. People that fantasizes shooting criminals would be included.
The rest of your post is irrelevant or uninformed crap. Europe isn't USA. Don't assume it is.
Norway, Sweden and Finland have a relatively high amount of guns per capita compared to other industrialized countries. Mostly for hunting. I think that applies to Germany too but aren't really sure.
But there are a lot of limitations in freedom when it comes weapon ownership in the parts of Europe I know about, some I agree with and some I don't. That's life in a democracy.
Slashdot Mirror
Have to compensate for Chernobyl first, radioactive and poisonous particles rained down over large parts of Scandinavia.
Surströmming probably compensates for both radioactive and active radio effects, IF one can stand the stench and taste. Not rotten BTW.
I assumed there were a new effort towards a RISC V design with acceleration hardware suitable for self-driving vehicles (whatever that would be).
You are seriously posting that question on slashdot? Open source means anything to you? That's the big one.
And then there is the advantage of having an alternative to x86 and ARM that is widely supported, extensible and without license and patent (?) fees.
It can be reduced but AFAIK not be eliminated. Acrylamide is created in the roasting process.
And the blurb is wrong - acrylamide have been reduced in chips but not eliminated. This by improving the processing, controlling temperatures better etc.
You don't understand that by letting Ecuador get away with their childish game there may be more severe consequences than letting one of your "actual British bail jumpers" (Assange is one too FFS) walk free for a few more days. And it's much easier to keep watch when the location of the wanted person is known. Should they just let it slide by?
And it's absolutely abuse of diplomatic rules.
Discrimination in itself is allowed, only discrimination of a number of protected groups aren't. IOW "no shirt no service" is okay, "no n*ggers" isn't.
Because this is about criticism for a apparently stupid decision from a company with near-monopoly power for a certain market subset, not (as far as I've seen) claims of illegal censorship...
Just because you are anonymous you don't have to act stupid.
Yes but the mess is due to its longevity! Remember we are talking about an architecture released in the 70's and now being 40 years old.
Core instructions aren't outdated with a few exceptions (when designing AMD64 some old instructions were removed and some reused), some instructions aren't used much anymore but are similar and execute in the same execution units as new extensions, some are just supported but not optimized for.
Compare with the original ARM instruction set which was released later but have had more incompatible extensions (reusing the same instruction encoding) and even a very incompatible change to extend the address space.
I don't claim it's a beautiful design or that there aren't better ones just that it isn't too bad.
--
The main problem with x86 isn't decoding but finding the start/end of internal fields.
[0-x prefixes] [op] [R/M] [SIB] [disp] [imm]
([op] can also be a [0xf] [op] in processors after the 8086/8088 for extended instructions)
[0-x prefixes] [REX prefix] [op] [R/M] [SIB] [disp] [imm]
REX is a special prefix added with AMD64.
[0-x prefixes] [VEX prefix] [2|3 extension field] [op] [R/M] [SIB] [disp] [imm]
SIB field is available for certain R/M encodings, added with the 386.
x+rest of the instruction 15 bytes (maximum instruction length)
You are wrong. Dark matter and dark energy are used as they are the only things that help explain our observations of nature.
Yes our theories are still wrong. They will be until we can describe everything - something not likely to ever happen. That's science. What you are doing is hand waving without understanding the basics.
Currently there are no active warrants in that case.
Bullshit. He isn't important, he isn't dangerous and he doesn't know anything.
If he suddenly vanished the US would be blamed and that would be a greater price to pay than the value of having an unimportant egocentric bitch under control.
Did you remember to look up in the sky for black helicopters before posting?
Just because it haven't been done before doesn't make it strange.
Because they don't spend the money and effort because Assange is so important or because the crime is so severe.
They do it to signal to the world that while one can abuse the diplomatic rules to avoid punishment for a crime the UK _will_not_be_humiliated_.
Personally I'd think closing down the embassy and ending diplomatic relations with Ecuador would be better. But I'm not that diplomatic.
X86 isn't that bad. It's easier to decode than many other architectures, it's easier to make superscalar than many others, it support extensions of the instruction set. The last one is why we are still using x86.
X86 processors execute x86 instructions. They are x86 and only a subset of instructions aren't executed directly. There is no translation hardware unless you call the instruction decoding translation (technically correct) and then almost every processor made have/had translation hardware.
Instruction fusion? Used on RISC. Instruction splitting? Used on RISC. Detection of special cases? Used on RISC (e.g. r0 or r31 defined as zero). Those are all optimization tricks.
700 lawsuits != 700 cases of burns
Need to have access: Internet or any other network will do. No need for physical access.
Able to execute arbitrary code: many ways to do that.
Do you realize that Meltdown and the other Spectre exploits that made everyone rush to patch operating systems and user software require both access to a system and the ability to execute arbitrary code? In fact this looks like a variant of the Spectre family using another type of branch predictor manipulation.
can be exploited by an attacker to obtain potentially sensitive information
In other words, there is a one in a billion chance that an attacker would obtain something of importance.
Not in the given citation. Potentially means potentially, nothing more, nothing less.
The attacker needs to have access to the targeted system and they must be able to execute arbitrary code
In other words, a completely worthless exploit.
Getting arbitrary user code running is relatively easy and any exploit that can bypass any kind of protection from a user mode program is a real problem.
So two out of two wrong. Better luck next time!
Well current solutions do use raster graphics - but I'd be very surprised if realtime raytracing didn't use it too. Representation -> Renderer -> Framebuffer -> Screen.
You are of course right about the misuse of the term.
There have been at least one polygon renderer that didn't use a framebuffer (don't remember the name/company) but with severe limitations: for every rendered pixel a hit test had to be done with every polygon which strongly reduced the numbers of renderable polygons. Add the problem of "racing the beam" and even with pipelining polygons had to be stored in expensive SRAM memory as variable latency couldn't be hidden. I'd prefer a framebuffer.
No those that know the stuff pointed out the problems with such types of engines, a kind that was known and tried but not used as polygon engines were simply put superior. Sampling artifacts, memory use, inflexibility due to extensive pre-processing...
Early demonstrations of the engine show some limitations (even though demonstrations tend to hide problems as much as possible), repeated objects aligned the same way to decrease memory needs, no moving sprites etc. Later demonstrations showed sprite type objects but with limitations (IIRC axis aligned only), more variation in models etc. but then computers were faster and had more memory. Later still I saw it was to be used as a point cloud renderer, possibly the best use of something like that.
But again the problems with such rendering techniques are well known, it isn't used as it isn't good for most things.
AFAIK Aureal did a limited form of this for their 3D soundcards. IIRC tracing a few "rays" in a simplified world model to simulate reflections etc.
No.
Brands?
Not a social experiment.
First you aren't the world - maybe you should take some LSD? Second you are most likely wrong.
Again with the ego. Maybe others have other definition that is more generally accepted? Maybe this is a step towards defining "self"?
Disgusting! You must have a really low intelligence to even think to write something like that.
While the music industry should be punished for blatantly lying about damages I don't have any sympathy for this individual assuming he earned money or other compensation for running this operation.
Jury nullification is a tool not to be used lightly - otherwise mob justice is the result.
Need: target shoots, hunts. Personal protection isn't part of a need - if there is a persistent need for protection it will be provided by the state. Some exceptions apply.
People prone to violence or have another condition that can make them hurt themselves or others. People that fantasizes shooting criminals would be included.
The rest of your post is irrelevant or uninformed crap. Europe isn't USA. Don't assume it is.
Norway, Sweden and Finland have a relatively high amount of guns per capita compared to other industrialized countries. Mostly for hunting.
I think that applies to Germany too but aren't really sure.
But there are a lot of limitations in freedom when it comes weapon ownership in the parts of Europe I know about, some I agree with and some I don't. That's life in a democracy.