leeter

23 ms·

211.
by leeter 5y ago
I played around with the godbolt he put up, I honestly found that adding __restrict to the pointers appears to make the biggest generated code difference and the code seems to be written with that in mind. That does ruin portability sadly,
212.
by leeter 5y ago
nVidia and Sony actually cited this patent I'd think you'd need to look further back. I'd guess Cray? This seems like something they would have patented very early on with the Cray1.
213.
by leeter 5y ago
Facebook's use of this pattern prevented me from attending my grandfather's funeral (live streamed on facebook because of COVID) earlier this year. I was to say the least... pissed. If not for my sister who re-broadcast it to me o
214.
by leeter 5y ago
I personally think the better solution is going back to how copyright worked pre 1976, where copyright had to be positively asserted to exist and everything else went into the public domain. I'm also of the position that a 'make a
215.
by leeter 5y ago
They make money off the one uploaded and inappropriately claimed until they release the claim (and the money) or decline the counter-claim. They also have an option to claim a strike against the flagged work.
216.
by leeter 5y ago
I think the thing that I've come to the conclusion with CISC and specifically x86 is that it's basically a better VLIW than VLIW. That's not to say there aren't opportunities with x86's memory model. To me the great
217.
by leeter 5y ago
Seems like an LGR oddware candidate, along with other eyeopener devices like this.
218.
by leeter 5y ago
That's what I'd assumed when I started skimming the spec, but the section I referenced seems to indicate a max of four regardless. I've never heard of a JPEG that's not RGB(A) or CMYK. So it would be highly unusual, not
219.
by leeter 5y ago
Skimming the JPEG spec I think the commit author was waaaay off base. The actual spec is very clear that 4 components is the max and are expected to be sequential in nature (4.11 Summary of coding processes) unless I'm reading it wrong
220.
by leeter 5y ago
They weren't horrible either, AArch64 is incompatible with AArch32 but you can still implement both on the same chip with shared internals. AMD didn't have to extend x86 the way they did, but without buy in from intel there was no
221.
by leeter 5y ago
Based on the docs kernel mode drivers would call KeWaitForMultipleObjects instead it appears. User space should just call WaitForMultipleObjects. While NtWaitForMultipleObjects and ZwWaitForMultipleObjects exist they seem to be undocumented
222.
by leeter 5y ago
As a native of a very well known mountainous state I can say it's more than that. If you're summitting on a mountain you need to be prepared to bivouac at least one if not two nights and survive adverse weather. Even experienced h
223.
by leeter 5y ago
In my experience the executives want what the sales folks want. What the sales folks want is features, preferably features that work half the time so they can include a support contract on top of the license. So they can fix bugs and get pa
224.
by leeter 5y ago
This is quite interesting. I've debated for awhile trying to write a "UEFI DOS" for awhile. Thus far I've always shied away because of the sheer immensity of just getting a UEFI dev env set up much less one that would su
225.
by leeter 6y ago
Not relational but IBMs Information Management System (IMS) comes to mind. https://en.wikipedia.org/wiki/IBM_Information_Management_Sys... dBase appears to be the first DBMS for minicomputers however.
226.
NZXT Recalls H1 Cases for Fire Hazard with PCI-E Riser(tomshardware.com)
1 points by leeter 6y ago|0 comments
227.
by leeter 6y ago
Windows does it because the vast majority of functionality is not implemented in the kernel per se, but rather in user space by preference for stability. Even things like display drivers are often primarily implemented in userspace. The mai
228.
by leeter 6y ago
You completely missed the point, multiple release builds doesn't actually fix the problem of emulation not having the same behavior or timing. That has a big impact on software cert for purpose and could completely torpedo an entire pr
229.
by leeter 6y ago
Example: The Commodore 128 (or the Plus/4 works too). The C128 had a more powerful CPU capable of 16-bit work, accessing more RAM, faster Disk access etc. But in general it was rarely targeted. Why? Because developers were looking for
230.
by leeter 6y ago
Not as simple as it sounds, HANDLEs are universal on windows. So it requires user mode code to both be in on the charade and to play nice, which it rarely ever does. The issue being things like GetWindowHandle, CreateMutex etc. Passing a Mu
231.
by leeter 6y ago
Mostly true, this would be protected mode 16bit code (286), not DOS code or real mode code. Protected mode 16bit code was rare and thus support was less needed.
232.
by leeter 6y ago
So unfortunately people do care, it's why 32bit windows is still a thing. Most of the people that care however are large legacy enterprises that are running line of business applications that they don't have the source code for or
233.
by leeter 6y ago
> It was a political choice by Microsoft to drop 16 bit Windows support in 64 bit Windows. This is the limit of their famous backwards compatibility -- still impressive, though. No... it wasn't political. It was a deliberate design
234.
by leeter 6y ago
People forget that Big O is only part of the story, they also need to consider Little o and average runtime. Just because something is n^2 or worse asymptotically doesn't mean the average runtime will be that bad. There are many cases
235.
by leeter 6y ago
A few things worth reading on the topic: Why the C++ committee didn't go with 'Stackful coroutines AKA Fibers' http://www.open-std.org/JTC1/SC22/WG21/docs/papers/2018/p136... Ray
236.
by leeter 6y ago
It's worth noting that this recommendation has nothing to do with delivered power.... a 500W can handle most systems on delivered power. This has to do with transients, the 3000 series cards have some massive transients that can easily
237.
by leeter 6y ago
Removed
238.
by leeter 6y ago
So it sounds like the games were probably doing too much in the re-implementation (60FPS isn't necessary for a DOS game). To answer the question: >Is there any hope of actually getting the promised performance out of modern hardware
239.
by leeter 6y ago
I remember a prior boss of mine was once asked if our reporting product could use PDF as an input. He chuckled and said "No, there is no returning from chaos"
240.
by leeter 6y ago
Yeah my first thought was just running a 16bit OS on modern hardware (it will do it if you're careful and do the right things). But then the issue of it being an ISA card popped up... that's not really a solvable problem with mode

More ›