06:13 <geist> Ermine: no i dont think so

06:13 <geist> or at least not the recent one

06:14 <geist> i remember someone piddling with it before but it wans't me i dont think

15:05 <ZetItUp> i have no idea how people managed to debug stuff when doing osdev before emulators, some stuff you can't find out is insane

15:05 <ZetItUp> did they send debug to prints? :D

15:05 <zid> serial po`rt

15:05 <ZetItUp> printers*

15:06 <zid> if you have a serial port you have full gdb

15:06 <zid> There's a reason everything is a tty ZetItUp

15:06 <zid> because they're emulating physical teletype printers

15:06 <ZetItUp> ooh

15:07 <zid> https://www.youtube.com/watch?v=2XLZ4Z8LpEE

15:07 <GeDaMo> Luxury! :P

15:10 <ZetItUp> thats cool but im not sure if i would have the patience for that :D

15:10 <zid> There's a reason people had to, you know, invent things like "text editors"

15:10 <zid> tools were bad + hardware was bad, and both slowly got better

15:10 <zid> because it was less painful to write better tools

15:11 <zid> because you had better hardware running better tools

15:11 <zid> repeat

15:12 <ZetItUp> makes sense yeah

16:27 <ddevault> most early computers had lights showing their internal states (registers) and buttons to single step the whole machine

16:27 <ddevault> for debugging

23:52 <Ameisen> The GCC docs specify: "Note, the ms_abi attribute for Microsoft Windows 64-bit targets currently requires the -maccumulate-outgoing-args option." so... does that mean that if I have a some generated or hand-written code that was for Win64, I cannot just have it be ms_abi without breaking ABI compatibility for the whole program when building for a SysV target with GCC?

23:53 <Ameisen> or is it specifically only for Win64 targets as it says? Now I've noted I'm not even sure if ms_abi works on non-Windows targets with GCC.

23:55 <Ameisen> Well, I'm noting that it _appears_ to work as expected.

23:55 <Ameisen> https://godbolt.org/z/P56boMG94