Search
Friday, 14th of January 2022, 17:29:07 UTC
17:33:45
Bike
0.053s read 0.046s write on sbcl, so we're getting close to I/O speed limits. cool.
17:43:05
Bike
let me just extend it for >8 byte and then i'll push
17:43:10
drmeister
What does the sample code look like?
17:43:22
Bike
the code i'm using to get times, you mean?
17:43:41
Bike
really dumb. just (loop repeat 1000000 do (read-byte stream))
17:45:25
drmeister
Regarding profiling. I learned that AMD has it's own profiling application.
17:45:41
drmeister
https://developer.amd.com/amd-uprof/
17:46:36
drmeister
It has a command line tool to gather data and a GUI for visualizing the data. It support Windows, Linux and FreeBSD.
17:47:19
drmeister
It has flame charts but you need to use the GUI to generate them from the data the CLI tool gathers. AFAIK
17:51:27
drmeister
It's probably why AMD perf support is weak - they put their energy into their own tool.
17:52:57
drmeister
My problem with it is I have to get X-windows working on zeus to visualize flame graphs.
17:53:32
drmeister
OR install Windows and use Linux subsystem for Windows to generate data and Windows to visualize it.
17:53:48
drmeister
Windows virtual machine maybe.
17:54:12
drmeister
Wait - no - that's still gonna require X-windows. Bleh.
21:53:48
Bike
signed byte streams are screwing me up and i don't understand it
22:43:26
Bike
don't know what's happening there. but they were broken already, so i just pushed the stuff to do unsigned I/O faster
23:28:51
Bike
i cannot make read-byte return a negative integer. i do not understand.
0:01:32
Bike
probably printf debugging time, but it's also a signedness problem so i have to make sure printf gets the right format string... eck...
4:43:26
Bike
drmeister: does build still use LTO? i haven't been able to build clasp on my home system without my computer locking up, and there's a new bug report complaining about the same thing
Saturday, 15th of January 2022, 5:29:07 UTC