fweimer

32 ms·

481.
by fweimer 2y ago
The hyperscalers are only efficient when compared to typical corporate IT departments, and what they can buy on the open market. For example, some analysts suggest that AWS EC2 has an operating margin of around 30%. If we take what off-bran
482.
by fweimer 2y ago
XSLT 3.0 defines an XML representation for JSON documents: https://www.w3.org/TR/xslt-30/#json I'm not sure how fun it is to work with in practice, given that the XML representation is quite verbose.
483.
by fweimer 2y ago
> The Pi 5 drops support for 32-bit ARM code Note that EL0 (userspace) support is still present, but RISC OS cannot currently run entirely in userspace.
484.
by fweimer 2y ago
This is a common misconception. The Classpath exception only applies to the class library, not to Hotspot (the core of the JVM implementation). The class library is also more tightly integrated with Hotspot than it used to be. And of course
485.
by fweimer 2y ago
GCC does not ignore inline for inlining purposes: Need a way to make inlining heuristics ignore whether a function is inline https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93008 (Bug saw a few updates recently, that&#x2
486.
by fweimer 2y ago
That's the other direction (legacy charset conversion to UCS-4 or UTF-8). This other direction is often reachable using the charset parameter in the Content-Type header and similar MIME contexts. HTTP theoretically supports Accept-Char
487.
by fweimer 2y ago
Some of the dependencies/vendored code are GPL version 3 or later (see e.g. https://bitbucket.org/rileytestut/gba4ios/src/master/emu-ex-... ). This license may require handing over signing keys in th
488.
by fweimer 2y ago
No, I think -Wl,--gc-sections still produces unwind data for the functions that remain. I suppose you could use the strip command on relocatable (intermediate) .o files. But the most common approach is probably building with -fno-exceptions
489.
by fweimer 2y ago
For a professional race car, I don't think safety is an overriding concern, given its intended use case. I think the late Robert Dewar (of AdaCore fame) made a similar comment about fighter jets: Is it really a domain for safety-critic
490.
by fweimer 3y ago
The unwind tables are in an allocated section and cannot really be removed after the final link (it would change file offsets in places that had their relocations relaxed, without a trace). These unwind tables are separate from the debuggin
491.
by fweimer 3y ago
If it really originated in the Lisp context (as someone claimed here), it's because it's about as much about eliminating unnecessary data and metadata as it's about executable code.
492.
by fweimer 3y ago
I wonder if the toolchain generated unwind tables. It's not unusual to disable them in embedded contexts. Without them, the DWARF-based libgcc unwinder won't worm, obviously.
493.
by fweimer 3y ago
Exactly. Something is very fishy if this system only writes 1.6 GB/s to the page cache. Probably that dd command line quoted in the article is incomplete.
494.
by fweimer 3y ago
With current concurrent collectors, the stop-the-world pauses are so short that they approach the pause times processes encounter for other reasons on untuned systems. But I meant something else: it's not always clear whether low-pause
495.
by fweimer 3y ago
Modern collectors have stop-the-world pause times in the millisecond range (aiming for less), even for very large heaps. Allocating threads may also incur allocation stalls, also in the millisecond range. However, these collectors need addi
496.
by fweimer 3y ago
The -fno-extended-identifiers option seems to do something in this area, but I don't know if it is sufficient. But it may block some characters which are used in standard English (for some values of standard).
497.
by fweimer 3y ago
Docker Engine is the name for the compiled binaries, right? The licensing situation for them must be more complicated than suggested by that LICENSE file.
498.
by fweimer 3y ago
Moby is open source. The licensing situation for Docker Engine is unclear.
499.
by fweimer 3y ago
Anyone installing a distribution package will be impacted eventually. https://qa.debian.org/popcon.php?package=redis
500.
by fweimer 3y ago
Banksy apparently runs a licensing program. Their artwork is most definitely under copyright, and they rely on trademark protection as well. There is also the practical issue that a lot of content is posted publicly without consent of the c
501.
by fweimer 3y ago
The signal comes from a safe fetch, which is just a read that allows ignoring the fault as if it never happened. Such a signal is deliver synchronously, so the usual restrictions for asynchronous signal handlers do not apply. The code in qu
502.
by fweimer 3y ago
The article fails to mention that __cxa_atexit allocates and therefore can fail, but the interface does not permit error reporting. This is probably more important to address for the thread-local destructor registration (__cxa_thread_atexit
503.
by fweimer 3y ago
The ISA manual is here: https://loongson.github.io/LoongArch-Documentation/LoongArch...
504.
by fweimer 3y ago
Fedora & downstream build with -D_GLIBCXX_ASSERTIONS, which enables bounds checking for many of those operator[] calls (including std::vector). For tight loops, GCC can often eliminate the bounds checks, at least if you use size_t (or s
505.
by fweimer 3y ago
Is there really consensus that practical systems need to have lock lease timeouts?
506.
by fweimer 3y ago
Gradual lifetimes could be interesting, though.
507.
by fweimer 3y ago
Clicking around a bit leads to this: “ The 2012 settlement followed a landmark court ruling which found hundreds of mostly female employees working in roles such as teaching assistants, cleaners and catering staff missed out on bonuses whic
508.
by fweimer 3y ago
The underlying object type would still be mutable in this case, you just can't get a &mut reference to the object.
509.
by fweimer 3y ago
The commercial static analyzers I've seen generate false positives (bogus issues that just aren't there) and false negatives (e.g., unconditional out of bounds pointer writes if that particular piece of C code is ever executed). S
510.
by fweimer 3y ago
The runtime thing is the easy part. I was wondering about the stack probes, which require LLVM support. There's a comment in the sources that suggest it's still x86-only, but that may be outdated: “ //! Finally it's

More ›