Hacker News: winocm

New comment by winocm in "Anthropic's model naming, extrapolated"

winocm — Wed, 10 Jun 2026 20:42:39 +0000

Don't forget the word "epic" (in terms of the literary definition).

New comment by winocm in "Local AI needs to be the norm"

winocm — Mon, 11 May 2026 00:22:59 +0000

Perhaps I am the odd one out here, but a small part of me wants to see what happens when you run a proprietary SOTA model on a laptop.

New comment by winocm in "Show HN: Hallucinopedia"

winocm — Wed, 06 May 2026 22:50:35 +0000

https://halupedia.com/2048-united-states-presidential-electi...

Amazing.

New comment by winocm in "Canadian fiddler sues Google after AI Overview claimed he was a sex offender"

winocm — Wed, 06 May 2026 18:22:45 +0000

"AI can make mistakes, so double-check responses."

New comment by winocm in "Networking changes coming in macOS 27"

winocm — Mon, 27 Apr 2026 16:44:32 +0000

That just ended up inadvertently reminding me, Windows Vista is actually almost old enough to be at the minimum legal drinking age in the US.

Windows 8 is nearly a decade and a half old as well.

Time really does fly.

New comment by winocm in "An AI agent deleted our production database. The agent's confession is below"

winocm — Sun, 26 Apr 2026 18:59:04 +0000

This almost sounds like The Monkey's Paw by Jacobs.

How to Fingerprint Users

winocm — Wed, 01 Apr 2026 03:03:51 +0000

Article URL: https://paradisefacade.com/blog/2026/3/9/how-to-fingerprint-users

Comments URL: https://news.ycombinator.com/item?id=47596281

Points: 3

# Comments: 0

New comment by winocm in "System 7 natively boots on the Mac mini G4"

winocm — Sat, 29 Nov 2025 09:36:38 +0000

Kinda sorts. The systems that the "MacOS on CHRP" thing ran on had a very strange looking device tree, with some bizarre combination of PC and Mac peripherals.

  Apple Cobra Open Firmware CHRP 1.1 B3 built on 08/18/97 at 13:04:24
  Copyright Apple Computer 1994,1996,1997
  Copyright IBM Corporation 1996
  All rights reserved.
   ok
  0 > dev / ls 
  ff82ec18: /cpus
  ff82ee08:   /PowerPC,604e@0
  ff82f600: /chosen
  ff82f750: /memory@0
  ff82f8d8: /memory-controller@fec00000
  ff82f9d8: /openprom
  ff82fab8: /rom@ff000000
  ff82ff48:   /boot-rom@fff00000
  ff830060: /options
  ff830828: /aliases
  ff830c78: /packages
  ff830d00:   /deblocker
  ff8314c8:   /disk-label
  ff832090:   /obp-tftp
  ff835db8:   /mac-parts
  ff836578:   /mac-files
  ff837de0:   /fat-files
  ff839700:   /iso-9660-files
  ff83a148:   /bootinfo-loader
  ff83b7d0:   /xcoff-loader
  ff83c060:   /pe-loader
  ff83c7d0:   /elf-loader
  ff83da18:   /terminal-emulator
  ff83dab0: /rtas
  ff83dc70: /pci@80000000
  ff83ff38:   /isa@b
  ff8414e0:     /nvram@i74
  ff841ad0:     /rtc@i70
  ff842500:     /parallel@i378
  ff842988:     /serial@i3f8
  ff843020:     /serial@i2f8
  ff8436b8:     /sound@i534
  ff850288:     /8042@i60
  ff8515f8:       /keyboard@0
  ff854b88:       /mouse@1
  ff8554c0:     /fdc@i3f0
  ff858730:       /disk@1
  ff85bac0:     /op-panel@i808
  ff85bba0:     /pwr-mgmt@i82a
  ff85bed8:     /timer@i40
  ff85c070:     /interrupt-controller@i20
  ff85c250:     /dma-controller@i0
  ff85c738:   /pci-ide@b,1
  ff85d028:     /ide@0
  ff85db78:     /ide@1
  ff85e6c8:       /cdrom@0
  ff862e60:   /mac-io@d
  ff863468:     /scsi@10000
  ff865298:       /disk
  ff8660c8:       /tape
  ff8671b8:     /adb@11000
  ff867cb0:       /keyboard@2
  ff8685a0:       /mouse@3
  ff8687c0:     /escc-legacy@12000
  ff8689b8:       /ch-a@12002
  ff868b08:       /ch-b@12000
  ff868c58:     /escc@13000
  ff868e40:       /ch-a@13020
  ff869500:       /ch-b@13000
  ff869bc0:     /via@16000
  ff869cb0:     /interrupt-controller@40000
  ff869e70:   /cirrus@e
  ff86e2c8:   /pci1022,2000@f
   ok
  0 >

Refer to the "Macintosh Technology in the Common Hardware Reference Platform" book for more information, if you're curious about the Mac IO pieces.

The Motorola Yellowknife board seems remarkably similar to this system, as well as the IBM Long Trail system (albeit with Long Trail using a VLSI Golden Gate versus a MPC106 memory controller). Both of them use W83C553 southbridges and PC87307 Super I/O controllers.

The architecture is kind of weird, but the schematics on NXP's website can probably elucidate a bit more on the system's design.

New comment by winocm in "Recursive macros in C, demystified (once the ugly crying stops)"

winocm — Thu, 06 Nov 2025 06:57:57 +0000

Mildly related, sort of, one can prevent expansion of variadic macros as follows:

   #define printf(...)

   int (printf)(const char *, ...);

I keep on seeing many random code bases just resort to #undef instead...

New comment by winocm in "Snapdragon X2 Elite ARM Laptop CPU"

winocm — Thu, 25 Sep 2025 18:38:20 +0000

You also get "Program Files (ARM)" (including a complementary "SysArm32") on older arm64 systems too.

New comment by winocm in "New protein therapy shows promise as antidote for carbon monoxide poisoning"

winocm — Thu, 14 Aug 2025 21:38:18 +0000

If you want to download SARS-CoV-2, here you go: https://www.ncbi.nlm.nih.gov/nuccore/NC_045512.2

New comment by winocm in "Windows XP Professional"

winocm — Thu, 07 Aug 2025 23:14:29 +0000

The latter is known as a "twiddle" in BSD land.

(c.f: https://ftp.netbsd.org/pub/NetBSD/NetBSD-release-10/src/sys/...)

New comment by winocm in "A fast, growable array with stable pointers in C"

winocm — Wed, 06 Aug 2025 22:28:32 +0000

At least since maybe the DEC Alpha 21264. It could address 48-bits of VA space, but that comes with caveats due to PALcode specific intricacies.

I think VMS (or was it Tru64?) uses this mode, but many other OSes just use 43-bit or 40-bit addressing. Realistically though, I don’t think many users would be using workloads that addressed more than 38-bits worth of contiguous VA space in 1998-1999.

New comment by winocm in "Rust running on every GPU"

winocm — Sat, 26 Jul 2025 18:32:00 +0000

LLVM SPIR-V's backend is a bit... questionable when it comes to code generation.

New comment by winocm in "I write type-safe generic data structures in C"

winocm — Mon, 30 Jun 2025 23:01:40 +0000

Don't forget the infamous pattern used in some C projects too:

  struct foo decl = {
    .member = /* ... */
    .next = &(struct nested_pointer) {
        .nested_member = /* ... */,
    },
    .array = (struct nested_array[]) {
      [0] = { /* ... */ },
    }
  };

This pattern does not work in C++ as the nested declarations become temporaries.

New comment by winocm in "Simplest C++ Callback, from SumatraPDF"

winocm — Mon, 16 Jun 2025 01:43:36 +0000

Consider this implementation:

https://llvm.org/doxygen/STLFunctionalExtras_8h_source.html

New comment by winocm in "RDNA 4's “Out-of-Order” Memory Accesses"

winocm — Mon, 24 Mar 2025 05:12:24 +0000

Kind of. NIR is more oriented towards lowering and optimizing code for driver backends, as far as I know. SPIR-V is targeted towards the other end of the spectrum.

New comment by winocm in "Apple M3 Ultra"

winocm — Thu, 06 Mar 2025 01:37:51 +0000

Sounds about right.

VMS is the only OS (that I know of) that uses all 4 processor privilege modes.

Side note: The 21064 has such bizarre IPR mappings, the read values have lots of bits scrambled around compared to their write counterparts. This is likely a hardware design decision affecting the programmer's model, if I had to guess.

New comment by winocm in "Apple M3 Ultra"

winocm — Wed, 05 Mar 2025 21:54:08 +0000

The Alpha architecture was 64-bit from the very beginning (though the amount of addressable virtual memory and physical memory depends on the processor implementation).

I think it goes something like:

  - 2106x/EV4: 34-bit physical, 43-bit virtual
  - 21164/EV5: 40-bit physical, 43-bit virtual
  - 21264/EV6: 44-bit physical, 48-bit virtual

The EV6 is a bit quirky as it is 43-bit by default, but can use 48-bits when I_CTL or VA_CTL is set. (the distinction of the registers is for each access type, i.e: instruction fetch versus data load/store)

The 21364/EV7 likely has the same characteristics as EV6, but the hardware reference manual seems to have been lost to time...

New comment by winocm in "LeetCode but You Can Force People to Code in Light Mode"

winocm — Mon, 24 Feb 2025 17:30:49 +0000

You’re not alone. I do the same, but often I keep the text editor in dark mode but the rest of the system on light mode to help provide contrast.