Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
wilun
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
20 ms
·
31.
▲
by
wilun
9y ago
I think they recently put backs tons of kernel space code back in userspace (in recent versions of 10), probably because the quantity of discovered security vulns started to become really ridiculous.
32.
▲
by
wilun
9y ago
The timing and the wording makes it so I'm quasi sure this was MS & Qualcomm related, and not Apple related. For example it says "there have been reports that some companies may try to emulate Intel’s proprietary x86 ISA w
33.
▲
by
wilun
9y ago
Are there extensions with a stronger memory model by at very low cost (matching the one of x86)? If not, we might not get excellent perf with x86 emulated by arm in the multithread & multicore era we are.
34.
▲
by
wilun
9y ago
There are several aspect to the perf hypotheses you make, and I don't see why Apple could not design its own CPU with excellent perfs. Current Apple best CPUs are already performing very well compared to some Intel CPU. Not the faste
35.
▲
by
wilun
9y ago
Yes on Unix it can be interesting, if needing fork/exec to spawn children, to pre spawn an helper child process that will do just that. But that would just be because the fork/exec model is insane: with a posix_spawn (or CreatePro
36.
▲
by
wilun
9y ago
> "valid but unspecified state", not in an invalid state That's mostly a detail because you can't rely on that to do anything interesting. Basically you can assign a new value to the object, or just destruct it. Havin
37.
▲
by
wilun
9y ago
> As far as I'm aware moves are only done when explicitly asked for Certainly not. Move are attempted (in the sense that the move constructor/operator= will be called if it exists) from rvalue references. Those are for example
38.
▲
by
wilun
9y ago
In their next statement about the next person they kill: 'The Autopilot clearly both stated in vocal synthesis and by displaying on the internal screen: "WARNING - I'll attempt to kill you in six second". Yet the driver
39.
▲
by
wilun
9y ago
> It's very irresponsible for any company to do stuff like this. It's very irresponsible for regulation to allow them to do that. And statistically for us to vote for politics that are not against that kind of behavior. Big com
40.
▲
by
wilun
9y ago
Tesla always blame the "driver" (and publicly so, nonetheless) when they are killed by their "autopilot" (which is actually driving, that is fulfilling the purpose indicated by its name, despite being not very good at it
41.
▲
by
wilun
9y ago
I just read http://unix.derkeiler.com/Newsgroups/comp.unix.solaris/2008-... and it seems that they did not solve any problem at all; they don't allow overcommit, that's all. But they do not do anything e
42.
▲
by
wilun
9y ago
Overcommit is desirable because of the fork/exec model of creating processes; if a big one wants to spawn children, without overcommit you need to be able to recommit its VM size, regardless of how lightweight the desired child is. Sad
43.
▲
by
wilun
9y ago
Oh but there actually are ways to signal failure (flushing caches, etc.), and there probably could and should be even more, but still the OOM killer is "needed" as a last resort measure. I recently saw an interesting Windows VM
44.
▲
by
wilun
9y ago
> Also, 8th gen includes Kaby Lake-R, Coffee Lake, Cannonlake, and maybe Whiskey Lake hm what are they smoking exactly? I want some! :p
45.
▲
by
wilun
9y ago
Disclaimer; I don't work at Intel, nor in any other processor design house, nor in a fab, etc. And honestly, look at what is variant 1, before spreading uninformed opinion. It is fundamental to speculative execution. You can have som
46.
▲
by
wilun
9y ago
It's doubtful Intel would delay plans too much to work on such subject, and its even more doubtful the result would even be better for anybody: we would have to use the old completely unpatched chips for longer... It's better for
47.
▲
by
wilun
9y ago
Dialects are of limited uses, because they are dialects... New dialects are arguably of even more limited uses, because better languages now exist where the desirable characteristics are enforced not by using a dialect, but by the core lang
48.
▲
by
wilun
9y ago
IEEE binary floating point is deterministic. There is no such thing as tolerated errors in compliant implementations. Non-compliant implementations are widespread for performance reasons, but that is a completely different story. Also I
49.
▲
by
wilun
9y ago
Yep, it seems people need to understand the details of base translation before writing a comment :p Anyway, IIRC you can round-trip 15 decimal digits correctly with an IEEE double. Don't know if it's floor(15.955) or something els
50.
▲
by
wilun
9y ago
Note: planned obsolescence is illegal in France. I think French customers would have a quite strong case to make under that law. Sonos gives the possibility not to upgrade, so they might get away with it, but it's hard to know in advan
51.
▲
by
wilun
9y ago
It will very probably not be double caches and nothing that kind of order for requested new silicon area. Its only an annoyance because the design are not gonna change for solid Spectre resistance (at least for its currently known versions
52.
▲
by
wilun
9y ago
That's an interesting summary but I predict that Linus will destroy him for completely avoiding the hard question: why the fuck IBRS_ALL would not be on by default on future "fixed" chips, if on such CPU it would not be someh
53.
▲
by
wilun
9y ago
It's not about generating the exception. It's about not operating on privileged data. (And not loading it to registers seems a good way to not operate on them, btw)... Generating the exception can still obviously happen at retir
54.
▲
by
wilun
9y ago
Because you came up randomly with your disappointment absolutely unrelated to today's topic, I'm tempted to give you another unrelated news: the Linux project has stopped using Bitkeeper too.
55.
▲
by
wilun
9y ago
Windows has vastly different policies for RAM allocation and commit than Linux. Windows basically does not overcommit while Linux systems not only does it by default but quite depend on it for various loads to work properly. In consequence,
56.
▲
by
wilun
9y ago
> In other words, you'd need about 16GB just to store the program to compute the permutation! Another way to reach this number is simply to consider that most reversible operations are going to be implementable by non-compressible L
57.
▲
by
wilun
9y ago
> Thus they decided to do permissions checking in parallel with other operations, leading to Spectre No. Leading to Meltdown. Spectre is fundamental to the way we approached any speculative execution until now.
58.
▲
by
wilun
9y ago
The microcode updates can typically be stored and loaded by the motherboard fw, though, and some OSes don't even load their own version.
59.
▲
by
wilun
9y ago
I don't think this is correct at all. I've personally seen the contrary happening. EDIT: however for some rare features, it is preferable to have them loaded by the firmware. I don't know if this is the case here.
60.
▲
by
wilun
9y ago
It's now called coordinated disclosure, for reasons. And, correct me if I'm wrong, but apparently calling Linus Torvalds and Greg KH the general public (as far as Spectre and its (poor for now) mitigations are concerned) is the ne
More ›