Conversation
2) remove the SIGKILL handling, since this will never get caught in userland
o.mp4Cannot beat the quality of a 40-year old PC speaker! 🥇 |
|
Thanks for the update!
True, but also only the two signals that are specified in calls to |
|
There can be a C function provided by the compiler or ELKS source code that does the beep. It could be added to https://gitlab.com/tkchia/libi86 of @tkchia . Hmm, the libi86 has been moved from github to gitlab. |
Hi @toncho11, I think this is same as I mentioned in the initial commit: Yes, outputting |
3 participants
We are now exactly with 1024bytes of the executable on x86_16: 0x3c0 for
.text, 0x10 for.dataand 0x30 for.bssMain sizes analysed by map-files in
.textare in almost same sizes:atolusleepldivfrom ia16-ldivmodu.o andudiv/umodfrom libgcc.a)IMO removing the switch/case from
beep_signalwould deterior code readability, since now it's easy to catch what is handled and what not. Your mileage may vary, it would save only 16 bytes, though.Happy beeping!