Raito_Bezarius has quit [Ping timeout: 260 seconds]
heat has joined #osdev
MiningMarsh has quit [Read error: Connection reset by peer]
<kaichiuchi>
hi
<gog>
hi'
Raito_Bezarius has joined #osdev
pounce has quit [Remote host closed the connection]
pounce has joined #osdev
Burgundy has quit [Ping timeout: 260 seconds]
sortiecat has quit [Quit: Leaving]
<kaichiuchi>
I'm deeply considering getting an old retro style setup
MiningMarsh has joined #osdev
<kaichiuchi>
you know, with the old 2000s era keyboards, mice, and the big CRT screen
<geist>
fascinating that old 2000s era is retro
<geist>
but alas, i'm too old
<kaichiuchi>
man i get you
wootehfoot has quit [Quit: Leaving]
<kaichiuchi>
i just want the old stuff to see how fast I can make something work on the old shit
<geist>
well as someone that deals with a lot of retro computer nostalgia, the answer is not very fast
<geist>
the appeal wears off pretty fast if all you're trying to do is run modern stuff on old hardware
<geist>
where it gets interesting is running old stuff on old hardware, since that's something that you can/shouldn't/etc do now
<geist>
ie, dos on a 486. xenix on a 286, win95 on a pentium, etc
<geist>
OS/2 on a pentium
<geist>
that kinda stuff is fun because its a novel experience at least from modern stuff
<kaichiuchi>
well I don't mean making existing modern software work on old PCs
<kaichiuchi>
I just mean projects that I code
<kaichiuchi>
still, though, the answer is likely "not very fast"
<geist>
yeah, but still a fun exercise if nothing else
<kaichiuchi>
i like making things go fast, and my overall theory is if I can make "x" go *really* fast on old hardware, surely on newer hardware it will go even faster
<kaichiuchi>
of course, that isn't always true
<kaichiuchi>
("i like making things go fast" might've sounded a little cocky, it's not to say that no one here cares about that either)
<clever>
kaichiuchi: ive also seen the reverse happen, to the point of crashing
<kaichiuchi>
right
<clever>
kaichiuchi: there was an abnormally slow opcode on old x86, that NT? based kernels used for the timing loop
<clever>
but then modern cpu's sped it up, and also run at ghz, so the timing loop takes 0 ticks of the system timer
<clever>
and boom, division by zero!
<clever>
it got too fast, and broke
<kaichiuchi>
hm... I think I remember something about this
<kaichiuchi>
FIX95CPU?
<kaichiuchi>
that's not NT but I can definitely see what you mean
gog has quit [Ping timeout: 260 seconds]
Matt|home has joined #osdev
<mjg>
yo
<mjg>
is there a magic one liner to show all exported symbols which are not referenced anywhere by the binary itself?
[itchyjunk] has quit [Read error: Connection reset by peer]
SGautam has joined #osdev
gxt_ has quit [Read error: Connection reset by peer]
gxt_ has joined #osdev
gildasio has quit [Write error: Connection reset by peer]
gildasio has joined #osdev
GeDaMo has joined #osdev
SGautam has quit [Quit: Connection closed for inactivity]
lkurusa has joined #osdev
lkurusa has quit [Quit: I probably fell asleep (or went out). Who will ever know.]
wootehfoot has joined #osdev
lkurusa has joined #osdev
gog has joined #osdev
lkurusa has quit [Quit: I probably fell asleep (or went out). Who will ever know.]
ptrc has quit [Ping timeout: 255 seconds]
ptrc has joined #osdev
V has quit [Read error: Connection reset by peer]
dequbed has quit [Read error: Connection reset by peer]
V has joined #osdev
dequbed has joined #osdev
Burgundy has joined #osdev
<gog>
meow+
ss4 has joined #osdev
wootehfoot has quit [Ping timeout: 265 seconds]
<moon-child>
meow-
<gog>
meow++
<moon-child>
meow#
<gog>
c# is ok
sortiecat has joined #osdev
<moon-child>
I have literally neve rused it
<gog>
i've grown to like it a lot
<gog>
way harder to shoot yourself in the foot with memory management
<moon-child>
afaik, c# is microsoft java, with a worse compiler and a slower gc, and possibly nicer syntax sugar
<gog>
that's basically true
<moon-child>
well yea, you get that with any gc language
<moon-child>
even rust
* moon-child
speaks softly to avoid awakening the resf
<j`ey>
but rust isnt gc??
bgs has joined #osdev
vdamewood has joined #osdev
<Mutabah>
moon-child: rust doesn't have gc
<Mutabah>
well, not any more
<Mutabah>
(long ago, in early 2014 it did... in name mostly)
<moon-child>
more's the pity--they removed it
<moon-child>
Mutabah: the implication was that even though rust is not a gc language, it still makes it way harder to shoot yourself in the foot with memory management
<j`ey>
true
<Mutabah>
"memory safe" is the term you probably wanted
<moon-child>
I was echoing gog
<Mutabah>
ah, misread the message associations
<gog>
yes memory safe
<gog>
also TIL c# has 'unsafe'
<moon-child>
so does java--sun.misc.unsafe
<gog>
i was wondering if it was possible to manipulate pointers directly and apparently so
<moon-child>
and haskell--unsafePerformIO
<moon-child>
and basically every other serious 'memory-safe' language--need escape hatches to get work done
<gog>
yeh
<gog>
part of me considers that a deficiency
<gog>
the part of me that says "fuck memory safety yolo"
<moon-child>
see church-turing, rice, etc.
<moon-child>
it's literally impossible to prove the correctness or memory safety of arbitrary programs
<gog>
yeh
<vdamewood>
Yum, memory
* vdamewood
eats all the memory
* gog
gives vdamewood a memory fishy
* vdamewood
chomps memory fishy
<vdamewood>
Wait... It's supposed to go the other way.
<gog>
it's actually a 32-bit number 0x68736966
<vdamewood>
gog: Your fishy is little endian.
<gog>
yes
<moon-child>
little endian best endian
<vdamewood>
Well, it's not like I have any big-endian machines anymore.
<vdamewood>
My last big-endian machine was a SparcStation IPX
<gog>
don't you have arm
<gog>
i know that's not exactly pure big endian
<gog>
but it will do it
<vdamewood>
ARM is little endian.
<gog>
what about BE8
<gog>
or is that an optional extension
<vdamewood>
Actually, I think ARM is bi-endian, and little is the default.
<gog>
in any case moon-child is right
<gog>
little endian best
* vdamewood
must... avoid... kink... okes.
<vdamewood>
*jokes
<gog>
kink jokes
<gog>
:o
<gog>
oh
<gog>
oh god
<gog>
no
<vdamewood>
gog: no?
<gog>
lol
<vdamewood>
Yay, I made someone laugh.
<kaichiuchi>
hi
<vdamewood>
hi
Ellenor is now known as Reinhilde
gildasio has quit [Ping timeout: 255 seconds]
gxt_ has quit [Ping timeout: 255 seconds]
gildasio has joined #osdev
gxt_ has joined #osdev
nanovad has quit [Quit: ZNC 1.7.5+deb4 - https://znc.in]
nanovad has joined #osdev
smach has joined #osdev
smach has quit [Read error: Connection reset by peer]
gildasio has quit [Ping timeout: 255 seconds]
gildasio has joined #osdev
gxt_ has quit [Ping timeout: 255 seconds]
gxt_ has joined #osdev
sortiecat has quit [Quit: Leaving]
smach has joined #osdev
vdamewood has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
ss4 has quit [Ping timeout: 265 seconds]
elastic_dog has quit [Ping timeout: 265 seconds]
elastic_dog has joined #osdev
heat has joined #osdev
<epony>
you're both insane, there is no little endianness
<gog>
where
<heat>
here
<heat>
gog, bazombie
<zid>
heat: day 11 was a total fuck
<heat>
a fuck? nice!
<zid>
impossible to parse and hard to solve
<zid>
I skipped the parsing and hardcoded it all into the source
<zid>
Also gmp is silly, I found out, and didn't even work
nyah has joined #osdev
<zid>
gmp revolves around a typedef of mpz_t.. but it's actually a scam type and is an array of [1] __mpz
<zid>
so it immediately breaks if you try to do things like assignment
<heat>
wait gmp?
<zid>
bigints yo
<heat>
ohno
<zid>
turns out gmp ran out of memory trying to solve it that way
<zid>
so I used a trick instead
<zid>
bitch level because it both wasn't free to implement, and also was impossible to parse
<zid>
either step is fine, both together sucked
<heat>
run someone else's python solution on your input and make your C program printf("<score>");
<zid>
system("./day11.py");
<zid>
full C source ^
<heat>
noooooooo not system!
<heat>
execve it man
<zid>
printf("<?php level11(); ?>");
<heat>
or CreateProcessW
<kaichiuchi>
i have to clean today.
<kaichiuchi>
and i don't wanna.
<kaichiuchi>
:(
<zid>
php would actually be a pretty good C pre-processor
<zid>
better than html
<zid>
better than using it for html*
<epony>
php is html pre-processor
<zid>
php not having you know, support, for html, is the weirdest shit btw
<zid>
you just have to echo "<br>"; all over
<epony>
you have to know when and how to use templates
<epony>
instead of generating the templates with code (duh)
<epony>
it's a magically stupid idea to generate HTML with C code either
<gog>
i will do it
smach has quit [Remote host closed the connection]
<mrvn>
zid: use the c++ wrapper if you want to do assignment
<radens>
Hello! Dumb as heck question. When I do a backtrace and gdb gets to the first frame, its shows this message: "Backtrace stopped: previous frame identical to this frame (corrupt stack?)
<radens>
"
<radens>
Is there a way to set up the stack frame such that gdb knows that, nope, that's the begining of the stack, it can stop searching there?
<radens>
I'm on aarch64 btw
<Mutabah>
debug information
<Mutabah>
add stack frame information for your asm entrypoint that marks itself as the end
<radens>
Mutabah: do you have an example of that?
sympt has quit [Ping timeout: 260 seconds]
<Mutabah>
Unfortunately, no.
<Mutabah>
Last time I tried to do DWARF debug info, it was for doing unwinding through IRQs/exception vectors
<Mutabah>
and gave up
<Mutabah>
Just doing a simple annotation of an asm function should be easy?