winocm

My condolences.

I had SIRS/sepsis once and it really is a harrowing experience. It really changed me forever and as a bonus, if not to add insult to injury, my hair now falls out and barely grows. Wouldn't wish it on my worst enemy.

Don't forget F77 codebases too.

Complete anecdote, but my personal life experience is that offices only cause me to get more easily distracted and forget what I'm doing (which costs me time and productivity), whereas at home I can actually concentrate and not lose track of my own mental models, leading to better results.

It's kind of sadly become necessary after having some traumatic brain injury, since I wasn't quite like this a decade ago.

It really depends on what you're doing and what dynamics the task at hand requires.

Off topic but tangentially related, here’s a fun fact, DEC Alpha actually ends up transparently converting IEEE single precision floats (S-float) to double precision floats (T-float, or register format) when performing registers loads and operations.

Ah, my favorite instructions, 'hw_ldl/l', 'hw_stl/c', 'ldl_l', 'stl_c' and their quadword siblings.

I guess the biggest difference is that Coldfire parts are still being produced (c.f: MCF52256CVN66).

I'm not sure if Alphas are even being made anymore, even 15-20 years ago.

To be fair, anything that does not support BWX is really painful to deal with.

Take, for example, an 8-bit/byte store. Without BWX the sequence would be something like:

        bic     a0, #3, t1
        and     a0, #3, t4
        ldl     t2, (t1)
        insbl   a1, t4, t3
        mskbl   t2, t4, t2
        bis     t2, t3, t2
        stl     t2, (t1)
        ret     zero, (ra)

But with BWX, it becomes:

        stb     a1, 0(a0)
        ret     zero, (ra)

DEC Alpha support is somehow still in the mainline Linux kernel...

In my experience, a LLM decided to not know type alignment rules in C and confidently trotted out the wrong answer. It left a horrible taste in my mouth for the one time I decided to look at using a LLM for anything and it keeps leaving me wondering if I'd end up more time bashing the LLM into working than just working out the answer myself and learning the underlying reasoning why.

It was so wrong that I wonder what version of the C standard it was even hallucinating.

Mastodon, but infrequently.

Honestly, I just quit using social media entirely for the most part.

It’s been really mentally liberating.

I took a cursory look at breaking it and it seems rather trivial in retrospect, just annoying at best since you have to rebuild the executable’s imports, relocations and section headers, along with removing the giant bloat sections that they add (seriously, when the main .text section of a game is 4MB, and then their extra obfuscation sections end up being over 250MB, something is ridiculously wrong.)

I feel like general press calling it “bird flu” over “highly-pathogenic avian influenza” (as what it is called in literature) might be a big oversight…

I still want to set up a copy of TeamWare SCCS… it seems to have several SunOS specific expansion extensions that are prevalent in many Solaris source files (such as %Z).

https://en.m.wikipedia.org/wiki/Sun_WorkShop_TeamWare

This is entirely possible. See copremesis, ICD10 code R11.13.

It usually occurs due to intestinal blockage or fistulae.

One heinous example is many implementations of '_FORTIFY_SOURCE', unless you want to resort to using lots of clang '__attribute__((__enable_if__(...)))' statements in your inline functions.

Also https://blog.petrieflom.law.harvard.edu/2022/03/15/ama-scope.... This mistake made some 20 years ago is a festering problem today.

Emergency surgery that probably would have invariably killed me since the organ was already gangrenous.

It got called "medically unnecessary" because apparently the person processing the claim couldn't read the fact that the organ was already dead and stopped at the line "stomach pain".

I had SIRS/sepsis right after that, it was fun.

Don't forget:

https://en.m.wikipedia.org/wiki/Friedman_doctrine

https://www.sciencedirect.com/science/article/pii/0304405X76...

Yeah, even integrating any C++ into it and calling any QEMU functions via extern "C" declarations when including the headers cause many issues because many variables are named "new" or have type cast issues.

It's a full time job on its own to fix all of the compilation errors. Could probably fix it with coccinelle scripts to make some parts easier, but still, validating the codebase with different compilers to make sure there's no resulting subtle breakage either still requires a lot of effort.

That is honestly how I actually see these things being used now, they can be powerful tools if used effectively.

The thought of people being replaced wholesale though…

This is increasingly reminding me of those dystopian science fiction films.

Reminds me about how many times I've ended up buying the same game I already own, but on another platform because the original is on something I no longer have reasonable access to anymore. (I don't have a television with a RF modulator handy and getting a proper setup working takes more effort than I'm willing to put in at this age.)

Pretty much.

Here's some declarations from an ancient UNIX (remember, UNIX(R) is a registered trademark of "The Open Group") ctags file to help show how that type of scheme works:

  ISDOT rm.c    /^#define ISDOT(a)      ((a)[0] == '.' && (!(a)[1] || (a)/
  Mrm   rm.c    /^main(argc, argv)$/
  PASS  rm.c    /^#define       PASS(byte) {                                    \\$/
  check rm.c    /^check(path, name, sp)$/
  checkdot      rm.c    /^checkdot(argv)$/
  rm_file       rm.c    /^rm_file(argv)$/
  rm_overwrite  rm.c    /^rm_overwrite(file, sbp)$/
  rm_tree       rm.c    /^rm_tree(argv)$/
  usage rm.c    /^usage()$/

Side note: https://unix.org/trademark.html

I learned of a cute side effect when one puts the function name on its own line, like above.

In BSD of yore and modern contemporaries, one could often perform `grep '^function'` and end up finding the source file quite easily. I think it also makes using ctags(1) a bit easier too, but not entirely sure on that bit.

Word of warning, I ended up getting a lot of strange compiler segfaults within xgcc when using when using `MKGCC=yes` instead `MKLLVM=yes` with NetBSD, specifically with floating point heavy code. I never did end up finding out why that happens.

Sure.

I basically did the following on trunk:

  $ CPP=/usr/bin/clang MAKEOBJDIRPREFIX=/private/var/tmp/obj ./tools/build/make.py  TARGET=arm64 TARGET_ARCH=aarch64 --host-compiler-type clang --debug -j17 --clean buildworld

You probably can follow build(5) from FreeBSD hosts instead.

NetBSD is similar, but you need to edit `tools/llvm/Makefile` and make sure that you use the following target for `support-modules` instead:

   support-modules: module-test.cpp Makefile
  -       if ${HOST_CXX} -stdlib=libc++ -c -fmodules -fcxx-modules -fmodules-cache-path=./module.cache \
  -          ${.CURDIR}/module-test.cpp  3> /dev/null 2>&1; then \
  -               echo HOST_SUPPORTS_MODULES=yes > ${.TARGET}; \
  -       else \
  -               echo HOST_SUPPORTS_MODULES=no > ${.TARGET}; \
  -       fi
  +       # Just don't use modules pre for C++20 targets. Some compilers cannot support them.
  +       echo HOST_SUPPORTS_MODULES=no > ${.TARGET};

You can further speed up NetBSD builds by editing `share/mk/bsd.sys.mk` and removing the workaround for SunPro's cc. The repeated invocation of /bin/mv for each object file really does add up.

I have not tried cross builds of OpenBSD from other operating systems.

The M3 Max laptops can cross-build FreeBSD at a fraction of the time of the ThinkPad, being at around 791 seconds for `make -j17` versus the T14s being at 3210 seconds (with `make -j12`) according to the post above.

No idea about power consumptions.

It still scares me.

Doctor mode...

There’s a similar story I’ve read before in a different paper regarding about an organ donor who drowned and then the recipient developed an extreme aversion to water.

I don’t recall what the exact title or link to the article was though.