mpe
Re:A Git story: Not so fun this time
on Thursday July 04, 2024 @07:28AM (#40874027)
This post is BS. You should delete it.
Re:AWS EC2 Virtualization 2017: Including Nitro
on Thursday November 30, 2017 @06:06AM (#15814893)
Zones are not VMs. If you need to vent your Linux hate at least save it for a post about Docker.
Re:Linus Torvalds: “Do No Harm”
on Wednesday November 22, 2017 @04:58AM (#15755633)
Depending on the bug class there may be users who never want "kill" to be the default option.
Re:PowerPC Notebook Block Diagram
on Sunday November 12, 2017 @04:54PM (#15682834)
That had basically nothing to do with the architecture. The key reason was likely the diverging requirements between laptop (Apple) and server (IBM) chips.
Re:50+ Segmentation Faults per Hour: Continuing to Stress Ryzen
on Saturday August 05, 2017 @09:14PM (#14939113)
That's a warning (~= assert()), not a segfault.
Re:A survey of BSD kernel vulnerabilities [pdf]
on Thursday July 27, 2017 @11:11PM (#14871659)
Yeah I agree. It would be great if parts of the kernel could be written in a safer language. I think in 10 years that will be happening in at least some widely used OS, but most likely one that only supports a small range of architectures.
Re:RISC instruction sets I have known and disliked
on Monday May 02, 2016 @06:22AM (#11610332)
At least with GNU as you can use %r1, %r2 etc. as an "intrinsic part of the syntax". Which means you can't use a register name where an immediate is expected.
However that doesn't fix the gotcha with r0 being special, that is specified in the ISA. In fact it's that way precisely so you can load an immediate without needing a separate opcode.