freenode/#sicl - IRC Chatlog
Search
7:40:48
Colleen
heisig: Bike said 10 hours, 16 minutes ago: i think an actual define-declaration analog would be out of scope for trucler. but trucler could have a function to read implementation-defined info for a user defined declaration, and maybe one to augment
7:40:48
Colleen
heisig: Bike said 5 hours, 43 minutes ago: the other trucler thing i probably need for cleavir to use it is being able to store arbitrary optimize info, like for client dependent qualities... i'll write a PR for that too i guess
7:56:31
heisig
::notify Bike The question is, should Trucler include functions for reading implementation-defined optimize info? Since they are implementation-defined, that particular implementation can simply subclass optimize-description and provide custom accessors.
9:38:26
heisig
Is 32.5 (error handling in standard functions) still up to date? It says that in SICL, standard functions shouldn't call other standard functions for the sake of precise error reporting.
9:44:04
heisig
Heh, also 32.7 (compiler macros) has been superseded by the recent advances in optimizing call sites :)
9:44:39
heisig
I am just pointing this out because it might confuse newcomers. They won't be able to tell which rule of the style guide is still relevant.
9:45:33
heisig
I am thinking of either rewriting them, or deleting them, or marking them as obsolete/work-in-progress.
9:45:42
beach
Now that no-defun-allowed is working on register allocation, I am trying to update the specification.
9:46:34
heisig
That would be wonderful. The specification is a great starting point for new developers.
9:47:22
heisig
So I will just write a new paragraph on designing protocols, and leave the cleanup to you.
16:11:03
Colleen
Bike: heisig said 8 hours, 14 minutes ago: The question is, should Trucler include functions for reading implementation-defined optimize info? Since they are implementation-defined, that particular implementation can simply subclass optimize-description and provide custom accessors.
16:11:42
Bike
i could have cleavir mandate that describe-optimize needs to return a special cleavir subclass of optimie-dscription, i guess
17:40:16
Bike
::notify heisig brief description of what i'm thinking wrt trucler optimize info https://gist.github.com/Bike/daa1bf795c8b718022856ac4cb15175a
19:31:12
jdz
There was a discussion about branch prediction here recently, so I'll just leave this here: https://blog.cloudflare.com/branch-predictor/
19:32:38
Bike
the "Obviously, this code could be improved" bit is a little weird to me because I'm pretty sure modern C compilers can rewrite that as a multiway branch/table lookup/whatever no sweat. sorta mentions that in the footnote though.
19:38:22
jdz
This sounds very good for all kinds of checks: "The takeaway is clear - you can have as many never-taken branches as you want, without incurring any cost."