Search
Monday, 10th of February 2020, 2:14:19 UTC
2:20:11
drmeister
When we switch to faso mode - .o files become .faso files and .fasl files become .fasp files. Is this a good idea?
2:20:46
drmeister
An alternative is to keep the .o and .fasl extensions but internally they both get the .faso/.fasp file format.
2:20:52
drmeister
This would work better with ASDF.
2:21:10
drmeister
Alternatively, we change ASDF
2:23:54
drmeister
No - I' changes to ASDF
2:24:37
drmeister
I'm not sure if it requires changes to ASDF.
4:03:10
beach
Good morning everyone!
11:09:57
kpoeck
drmeister as far as I understand, we can use .faso and .fasp files, as long as we handle them accordingly
11:10:15
kpoeck
asdf seems to use compile-file-pathname all over, hopefully no need to change
11:12:00
kpoeck
drmeister I tried to change ext:generate-encoding-hashtable to use a variable with a hash-table, but compilation time was much worse, need to experiment more
12:55:39
drmeister
I’ve got the faso files worked out I’d like to make them the default
12:56:47
drmeister
kpoeck: let’s take a look at it. Can you paste the generator code?
12:57:34
drmeister
Re faso - they avoid linking and they load just as fast as the current dylib fasls
12:57:48
drmeister
Also as fast as Linux so
12:58:14
drmeister
They are also less complicated than dylib fasls. And we control them.
12:58:41
drmeister
They don’t have the weird issues where debug info is split out on macOS.
12:59:44
drmeister
They are necessary for compile-file-parallel now. I disabled the object mode because it’s crazy complicated.
13:01:04
kpoeck
Can share this evening UTC+1 (am at day work)
14:10:56
Bike
so i can merge stuff again now, right?
Monday, 10th of February 2020, 14:14:19 UTC