IRC channel logs
2026-02-21.log
back to list of logs
<azert>it’s the second issue that Mike is working on happening only in 64bit? <azert>16bytes filled with zero point to an issue with sse registers and interruptions <sobkas>Someone loved global variables while doing hurd... <youpi>global variables do make sense relatively often <azert>sobkas: someone loved the linker a lot while making the Hurd <azert>like why spending boilerplate like anyone else do to define callback structures, when the linker can do that for you <azert>or maybe the logic was “what is so special about the main function” <sobkas>They also make code harder to understand <damo22>there is an alternative school of thought where globals are almost frowned on <damo22>ie youre supposed to create a struct and malloc it <azert>I think it’s a question of style. This style went out of fashion so it’s hard to get used to it <azert>maybe if you think translators as single implementations of classes, it makes more sense. Made more sense before the invention of c++ at least <damo22>but also, if you try porting translators to rust, you cant use globals the same way <damo22>because of the memory safety a function has to take control of memory pointers <damo22>nothing else can write to it while a function has the memory <sobkas>I would be ok with them, but they are put at random in different files so finding them is a bit tedious <azert>the rust people will have to wrap up everything if the want to write translators in rust <sobkas>I use them, but there is no global on hurd <damo22>sorry what do you mean there is no global on hurd <sobkas>apt policy global global: Installed: (none) Candidate: (none) Version table: <damo22>when you use ctags+vim, you can jump to the definition of any symbol easily <damo22>global isnt the name of a package, its a type of variable in a C file? <damo22>we were not discussing the package <sobkas> GNU GLOBAL is a source code tag system that works the same way across diverse environments <sobkas>I said I use gtags to search for global variables <sobkas>And because there is no global(package) it's hard for me to find them on hurd <nikolar>if you use vim, gd will automatically go to the first instance of the word under the cursor <nikolar>you don't even need external tools (i assume emacs has something similar) <sobkas>global variables are in dddifferent files <damo22>vim can jump between files with g] <damo22>then ctrl-t to return to where you were <damo22>emacs can probably jump to another file and then return too with the right key combo <sobkas>It can, when I use gtags, and because there is no global on hurd I can't use it there <damo22>but emacs supports exuberant-ctags <sobkas>I have my custom emacs configuration with lots of stuff in it that switching to ctags might be harder than fixing global package <damo22>i just have some colors i really like <sobkas>Ok if I do settrans -ac /servers/socket/1 /hurd/pflocal.prof before settrans -fg I get gmon.out <youpi>sobkas: global used to build fine on hurd-i386, it is available there. It shouldn't be hard to fix its compilation <yelninei>Hi, any idea why a dir_lookup on /dev/wd0 causes a complete freeze? <nexussfan>How come X doesn't work on Coreboot? Any technical reason? <azert>nexussfan: nobody worked to make it work yet <azert>damo22 made sure that the Hurd console can use the coreboot fremebuffer, X11 could do the same <azert>also may be that if you compile the vesa bios in coreboot, depending on your gpu, it might work already <sobkas>youpi: it was easy and I fixed it