pm215

29 ms·

361.
by pm215 4y ago
I don't take notes because I read primarily for entertainment, in both fiction and non-fiction -- I have no need to recall in detail the contents of a book or to tie them into some overarching system, because I'm not an author or
362.
by pm215 4y ago
Another approach to that kind of vague code requirement might be for compliance software to do automated checks and also spit out the list of for-human-checking items. If the permitting authority only has to do things like "check the s
363.
by pm215 4y ago
You might be interested in this recent Register opinion article, which (in passing) makes the point that Arm and x86 have thus far succeeded largely by concentrating on things the other is not doing rather than by directly trying to take
364.
by pm215 4y ago
It's not a PC in the very important "just boots Windows and runs my existing software" respect. That is what the overwhelming majority of purchasers in the "desktop PC box" market have as an absolute non-negotiable
365.
by pm215 4y ago
The answer to this is essentially that CPUs are only cheap if you make them in huge volume, and "I want something that's like a PC but not actually PC compatible" is a pretty small market, so an SoC designed and manufactured
366.
by pm215 4y ago
That's not what the expression does. It means "first increment argv (so it points to the thing at index 1 in the original argv array); then dereference it". (Contrast *argv++, which dereferences at the initial pointer value,
367.
by pm215 4y ago
Also, the "PC-losering problem" presented as one of the central examples in the original 'Worse is Better' really is an example of 'worse' -- the unix approach gives a modest reduction in kernel implementation
368.
by pm215 4y ago
A friend of a friend retired from the tech industry to become a joint-investor in a small chain of pubs. He ended up writing his own Linux-based POS software for the pub tills, AIUI...
369.
by pm215 4y ago
At what point in the application-and-interview process did you usually bring up the 4-day-week requirement?
370.
by pm215 4y ago
My experience is limited (couple of UK companies), but I've twice been able to negotiate down to 4 days as an existing employee without much difficulty, but found it much harder (failed) to negotiate starting at 4 days with a new emplo
371.
by pm215 4y ago
The way my UK employer handles this is to add N extra days to your holiday/leave allowance, where N is 80% (or whatever % of fulltime you work) of the number of public holidays in a year; then they require you to book any public holida
372.
by pm215 4y ago
We've switched to _Static_assert() now we can assume all our compilers support it: #define QEMU_BUILD_BUG_MSG(x, msg) _Static_assert(!(x), msg) #define QEMU_BUILD_BUG_ON(x) QEMU_BUILD_BUG_MSG(x, "not expecting: " #x)
373.
by pm215 4y ago
For contributions by new authors I usually don't make them do a respin for something minor, for instance if I think a more explanatory comment would be helpful -- I just fix those up when I commit. It saves the author doing multiple ro
374.
by pm215 4y ago
Generally the recipe will tell you to cook the fennel first, though, and will give timings so you can get it right. The problem with prep-on-demand is that if you start cooking the fennel and then are unable to prep the zucchini fast enough
375.
by pm215 4y ago
I do tend to cook like this, but that's because I'm an inexperienced cook :-) I don't trust my ability to complete a prep task in the bounded amount of time you have once you've actually started cooking, so unless the t
376.
by pm215 4y ago
I have a couple of machines lurking in my collection which worked fine the last time I turned them on, but that was 15 years ago now... I really should do the research on how to make sure I don't accidentally damage them by powering th
377.
by pm215 4y ago
Yes, absolutely you should have a point to make with your new architecture, and that's likely to involve at least some weirdness. What I'm trying to get at is that the weirdness budget isn't infinite, and therefore you want t
378.
by pm215 4y ago
It can still get you into some extra corner cases for the insn fetch hardware to have to handle when an insn crosses a cache line boundary, though...
379.
by pm215 4y ago
On endianness, I'm not making a claim that one or the other is "better" or "right" -- merely that little-endian architectures are pervasive in the current world, and so picking big-endian for a hypothetical new arch
380.
by pm215 4y ago
Some of Tokyo's elevated highways are an aesthetic disaster; the one that goes very low over the Nihonbashi bridge is the classic example. On the bright side they are finally planning to move that particular expressway underground...
381.
by pm215 4y ago
You could argue that Arm mostly doesn't get too weird and that that's part of why it succeeded, but some things include: + 'char' being unsigned + handling of unaligned accesses (in early architecture versions a value is
382.
by pm215 4y ago
I have a theory that CPU architectures implicitly have something I call the "architectural weirdness budget", which is the extent to which you can get away with design decisions in the architecture or ABI that differ from the exis
383.
by pm215 5y ago
The -devel list is dominated by patches just because that's how our workflow works; but if you have a technically focused question or one that's about the internals or the source code then you should feel free to ask it there (tho
384.
by pm215 5y ago
Yes, except that if the last digit is not 0 then it only tells you "this is on the stable branch that started at the x.y.0 tag", and says nothing about year or month. Stable branch releases usually happen about 4 months after the
385.
by pm215 5y ago
Personally I pronounce it "kwem-yoo" (first syllable starts like 'quest', second syllable like the second-person pronoun 'you'). But I think there are multiple pronunciations floating around...
386.
by pm215 5y ago
As the person who tagged v7.0.0 yesterday, I do in fact know our release cadence :-) As bonzini says, .0.0 is April, .1.0 August and .2.0 December. The x.y.1 are stable-branch releases which happen slightly more irregularly.
387.
by pm215 5y ago
The really big thing that gets me on macos is not having focus-follows-mouse and works-everywhere select-to-copy middle-click-to-paste. Yes, this is "just" a UI thing, and yes, I can more or less get used to the macos choices (I u
388.
by pm215 5y ago
It was simpler to just move from "major.minor and we bump the major infrequently and semi-arbitrarily when the minor is big enough to feel unwieldy" to "bump major for first release of the year" rather than completely ch
389.
by pm215 5y ago
QEMU releases are calendar-based, every four months, so "7.0" just means "first release of 2022", not "we got lots of new and shiny stuff so we bumped the major version" :-) More generally, what goes on in QEMU
390.
by pm215 5y ago
Similarly, instead of doing "a few hundred stepis" to get to the call insn that jumps to a garbage address, you can let execution run to the crash point and the reverse stepi once. The "reverse" functionality parts of rr

More ›