TLB Hit ๐Ÿ’ฅ

JF Bastien & Chris Leary
  • 5.0 (1)
  • เจคเจ•เจจเจพเจฒเฉ‹เจœเฉ€

A podcast about systems & compilers by @jfbastien and @cdleary. The only podcast you listen to at 0.5ร—.

เจเจชเฉ€เจธเฉ‹เจก

  1. Episode 6: ฦ‘แบษ„ส‘ส‘า‰โŸ†ฦ‘u๐”ท๐”ทโงซแถณฮฉ๐“•

    15/12/2024

    Episode 6: ฦ‘แบษ„ส‘ส‘า‰โŸ†ฦ‘u๐”ท๐”ทโงซแถณฮฉ๐“•

    In this episode, Chris and JF dive into the world of code coverage and fuzzing. They explore why coverage matters, the types of coverage metrics, and how fuzzing helps uncover unexpected software behavior. From the practical trade-offs of MC/DC testing to the randomness of AFL's mutators, the hosts discuss techniques, tools, and the balance between robustness and resiliency. Tune in for insights, laughs, and maybe even a recommendation to "go fuzz yourself!"

    28 เจฎเจฟเฉฐเจŸ

  2. 23/02/2023

    Parsers

    TLB Hit ๐Ÿ’ฅ

    42 เจฎเจฟเฉฐเจŸ
  3. Episode 4: t-r-a-c-/eฬ…โ€พ\-o-m-p-i-l-e

    06/05/2022

    Episode 4: t-r-a-c-/eฬ…โ€พ\-o-m-p-i-l-e

    Monitor. Compile. Bail. Repeat!

    38 เจฎเจฟเฉฐเจŸ
  4. __builtin_expect(!!(x), 0)

    19/04/2021

    __builtin_expect(!!(x), 0)

    * What is it we know statically? * What's effectively discoverable only at runtime? * How do we tell "the machine" (compiler and/or hardware): * Things we *know* to be true... * Things we *expect* to be true... * Things we *expect* to be true but *want to do something about* when it's not... * Things we have no idea about! * How do we collect that information that we have no idea about? * What happens if we're wrong? What if the workload is inherently irregular? * In the limit, random noise could drive our control decisions! * We talked a bit about precise vs imprecise exceptions before and automatic reordering, and we've mentioned vector machines and auto-vectorization. * All falls into the broader theme here, but we're always questioning what we can actually cover in an hour... * We'll try to give it a go for a subset of these things! * Time is often the limiting factor. * The episode title is the thing that we often macro define as `#define UNLIKELY` * In C/C++ code you might say "this control condition is unlikely", and say `if (UNLIKELY(condition))` * In C++20 there was added these `[[likely]]` and `[[unlikely]]` annotations that do the same thing, but with more square brackets, so clearly better!

    39 เจฎเจฟเฉฐเจŸ
  5. https://tlbh.it^M

    21/02/2021

    https://tlbh.it^M

    What happens when you type https://tlbh.it in your browser's address bar, and press enter?

    57 เจฎเจฟเฉฐเจŸ

  6. 23/11/2020

    *(char*)0 = 0

    The adventure of storing NUL to NULL!

    44 เจฎเจฟเฉฐเจŸ
  7. mov fp, sp

    02/11/2020

    mov fp, sp

    The stack, and how it relates to TLB Hits.

    1เจ˜เฉฐ 4เจฎเจฟเฉฐ
  • 7 เจเจชเฉ€เจธเฉ‹เจก

เจœเจพเจฃเจ•เจพเจฐเฉ€

A podcast about systems & compilers by @jfbastien and @cdleary. The only podcast you listen to at 0.5ร—.

เจœเจพเจฃเจ•เจพเจฐเฉ€

  • เจฐเจšเจจเจพเจ•เจพเจฐ
    JF Bastien & Chris Leary
  • เจธเจฐเจ—เจฐเจฎ เจธเจพเจฒ
    2020 - 2024
  • เจเจชเฉ€เจธเฉ‹เจก
    7
  • เจฐเฉ‡เจŸเจฟเฉฐเจ—
    เจธเจพเจซเจผ เจ•เจฐเฉ‹
  • เจ•เจพเจชเฉ€เจฐเจพเจˆเจŸ
    ยฉ Chris Leary & JF Bastien
  • เจธเจผเฉ‹เจ… เจฆเฉ€ เจตเฉˆเฉฑเจฌเจธเจพเจˆเจŸ
    TLB Hit ๐Ÿ’ฅ