Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
o11c
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
43 ms
·
661.
▲
by
o11c
2y ago
Note that the ZFS choice will break tools that check for sparseness and assume it's a binary file. Off the top of my head, the most famous breakage was GNU grep ... 2.14?
662.
▲
by
o11c
2y ago
Does a thief have the right to demand nobody re-steals what was stolen in the first place? If we accept the existence of intellectual property in the first place, all AI is blatant and unmitigated theft. If we do not accept it, Llama has no
663.
▲
by
o11c
2y ago
That is how `getaddrinfo` works under GLIBC; it's called NSS. The problem (well, one of them) is the non-GLIBC implementations that say "we don't need no stinkin' loader!"
664.
▲
by
o11c
2y ago
Hm, looking to see if the vendor field is actually meaningful ... I see some stuff for m68k and mips and sysv targets ... some of it working around pre-standard vendor C implementations Ah, I found a modern one: i[3456789]86-w64-mingw*
665.
▲
by
o11c
2y ago
Thankfully modern source control doesn't reuse user-supplied filenames for its internals. In the dark ages, I destroyed more than one checkout using commands of the form: find -name '*somepattern*' -exec clobbering comman
666.
▲
by
o11c
2y ago
The whole point of section names is that they mean something. If you give it a name that matches `.rodata.*` it will be part of the existing read-only LOADed segments, or `.data.*` for (private) read-write. Use `ld --verbose` to see what se
667.
▲
by
o11c
2y ago
Right, but you can just use the section start/end symbols for a section that already goes into a mapped segment.
668.
▲
by
o11c
2y ago
Having tried writing plugins for both, I very much prefer GCC's codebase. You have to adapt to its quirks, but at least it won't pull the rug from under your feet gratuitously. There's a reason every major project ends up emb
669.
▲
by
o11c
2y ago
Historically, when DNS breaks in a not-glibc environment, it's very often found to in fact be a violation of some standard by the not-glibc, rather than a program that fails to document a glibc dependency.
670.
▲
by
o11c
2y ago
Old versions of GCC used to provide `-b <machine>` (and also `-V <version>`), but they were removed a long time ago in favor of expecting people to just use and set `CC` correctly. It looks like gcc 3.3 through 4.5 just forwards
671.
▲
by
o11c
2y ago
"gnu tuple" and "gnu type" are also common names. The comments in `config.guess` and `config.sub`, which are the origin of triples, use a large variety of terms, at least the following: configuration name configura
672.
▲
by
o11c
2y ago
I wouldn't call them "same concept" at all. Segments (program headers) are all about the runtime (executables and shared libraries) and are low-cost. Sections are all about development (.o files) and are detailed. Generally t
673.
▲
by
o11c
2y ago
LLVM didn't invent the scheme; why should we pay attention to their copy and not look at the original? The GNU Config project is the original.
674.
▲
by
o11c
2y ago
The GNU scheme does in fact have support for various windows targets. It's just that the GNU compilers don't support them all.
675.
▲
by
o11c
2y ago
There are up to 7 components in a triple, but not all are used at once, the general format is: <machine>-<vendor>-<kernel>-<libc?><abi?><fabi?> But there's also <obj>, see below. Note th
676.
▲
by
o11c
2y ago
This article should be ignored, since it disregards the canonical origin of target triples (and the fact that it's linked to `configure`): https://git.savannah.gnu.org/cgit/config.git/tree/ The `testsu
677.
▲
by
o11c
2y ago
I recommend against global -Werror, instead use -Werror= with each individual option to make it much easier to deal with compiler upgrades that change warnings. For well-maintained code, -Werror=all is expected, but switching to it is not t
678.
▲
by
o11c
2y ago
In case anyone needs to do the sort of "fix up scattered declarations and move them to headers", you really want to use: gcc -Werror=missing-declarations -Werror=redundant-decls (last I checked, Clang's implementatio
679.
▲
by
o11c
2y ago
For the purpose of blurring, there's nothing wrong with linear RGB. HSL has the angle discontinuity which is really annoying to deal with and sometimes even impossible to work around. CIELAB should be fine in theory, but it's not
680.
▲
by
o11c
2y ago
It's really not. The multi-chunk arena it describes at the end of the article is exactly the same structure as GNU obstack, except that obstack also bothers to implement the free-to-mark operation. It's trivial to provide the oper
681.
▲
by
o11c
2y ago
> You can only deallocate everything in the arena, not individual parts of it. Untrue; this excludes the middle. GNU Obstack is a widely-used arena allocator with a "free everything allocated after this point" operation, among
682.
▲
by
o11c
2y ago
I mean, nobody should be surprised since Reddit drove away almost all of their moderators and power users in mid-2023 by banning clients that actually functioned. Reddit chose to kill itself; a maggot-ridden corpse is the expected find.
683.
▲
by
o11c
2y ago
You shouldn't spend your own effort; you should make it clear that you're open to users of such systems contributing. That's how GCC became so dominant - there were people already using all sorts of Unixen and they wanted a
684.
▲
by
o11c
2y ago
> stop buying things that have a prop 65 warning (I know prop 65 isn’t perfect, but it’s often a lead warning). Note that: * since 2018, the warning must include at least one specific chemical (but not all of them) * unlike initially, ma
685.
▲
by
o11c
2y ago
I see at least two evil things trying to load on that page.
686.
▲
by
o11c
2y ago
You can already do this. Just register the binfmt-misc with the `C` flag; binfmt-misc takes priority over builtin binfmts. Make sure your interpreter is very carefully written!
687.
▲
by
o11c
2y ago
Remember, according to the GDPR: * any strictly necessary cookies do not require consent * any preference/functionality cookies require consent, but the user has to go looking for them anyway Thus, preemptive cookie banners are only ne
688.
▲
by
o11c
2y ago
I do think that people are far too hesitant to bind member functions sometimes: statement_endpoint: Final = "/api/v2/accounts/{iban}/statement".format (it's likely that typecheckers suck at thi
689.
▲
by
o11c
2y ago
I was really confused by the mention of 68k at first since MacOS 8.6 dropped support for that, but following the link it looks like it supports System 7 as well. Cross-compiling would be faster (than emulation or too-old hardware), but I
690.
▲
by
o11c
2y ago
Is there any reason to ask this? GCC plugins have been good since 4.8. 4.5 lacked some essential features; 4.6 would be fine if not for the annoyance of trying to support a plugin that works across the C++ transition. Of course, you can jus
More ›