Tuesday 9th January 17:00 UTC

Main Agenda

  • reminder of only 6 weeks until march 1st deadline for completion of cavatools and cryptoprimitives.


  • will need volunteers for the devroom:
    • Watch speaker, keep track of time
    • Carry mic to audience, keep questions short
    • Watch the door, make sure talk doesn't get disturbed (people come in in the middle of a talk)
  • Make sure PDF slides for the talks are:
    • Uploaded to pretalx platform in good time (two weeks before FOSDEM?)
    • Resolution set to 1280x800 resolution, preferably 800x600.
    • Higher-res slides can be uploaded later, but for the actual slides to be used during the event, resolution must be as mentioned above.
    • Put all PDFs on the laptop to be used for presentations. Make sure we have copies just in case.
    • More info on slides from Luke: email archive

Meeting notes:


  • Came back from holiday yesterday.
  • Bug #1048, Cleaning up ls011 by using inline ld/st imports.


  • so, not a whole lot of news from me, i fixed a extra-parenthesis-in-a-wrong-spot bug for dmitry and fixed a bug luke left, but didn't actually make any coding progress beyond that.

During call, walked with Sadoon through assembler:

summary: discussing how to best split into sub-word chunks
for poly1305
> tbh dsrd isn't better than other shifts here
It did help with taking the shift remainders and stitching them together which shortened the code quite a bit
Also considering doing sv.dsrd instead of two dsrd's since we already use setvl=2 here
> sv.dsrd is 8 bytes, just like 2x dsrd 
But it's a good demo of setvl anyways
> yeah, being a good demo doesn't mean there isn't a better demo 
The better demo is the mul/adds 😃
> try using a different register than r0, the simulator may be treating that like (RA|0) and just using r0 in both iterations... 


  • Working through Poly1305 assembler.
  • Poly1305, bug #1157
  • Learned to use dsrd, done in first half of poly1305_blocks. Had issues with using sv.dsrd but it's kind of working now, will use it.
  • TODO: Make comments on bug #1157.

  • After that, work with the team on presentations as well as my own