libera/#clasp - IRC Chatlog
Search
17:02:23
drmeister
Bottom of page 324 - that's how I read it. But I think we don't let this influence us. Any weird bit width would be the responsibility of the programmer.
17:02:32
Bike
"Data are stored in a continuous stream of bits, with no delimiters", and it specifically contemplates 1 and 2 bits
17:03:56
Bike
so i'd guess how that code would actually be written is reading 8-bit bytes, or something, and then parsing those appropriately
17:09:39
Bike
okay. so i'll at least extend it to do any number of 8-bit bytes (below, i don't know, 1024). then maybe think about arbitrary bit widths. that's gonna be weird though.
17:24:41
Bike
old code reading 1M ub32s: 0.257s. writing: 0.269s. new code: reading 0.057s, writing 0.060s
17:27:35
Bike
that is, it read(2)s once for each ub32. so a million read(2)s. the old code would do four million.
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.
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
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