As far as I can tell from the jitter docs, no; the big thing about copy and patch is that you can piggy back on the existing C compiler and whatever backends it already supports.

> piggy back on the existing C compiler and whatever backends it already supports

that is the whole point of jitter

Does jitter compile C at run-time or just stitch it together? (EDIT: looks like stitch at run-time)

The other thing C&P does is allow for a library of stencils and stitch them together intelligently depending on where arguments are coming from, where the return should go, where the flow of control should go next, etc

EDIT: So I guess they look fairly similar, huh

yup, jitter does that too; e.g. https://ageinghacker.net/talks/jitter-slides--saiu--bts-2022... page 23 and 35

fwiw i thought this was a stupid, hacky, pointless approach when it was called jitter and i still think it's a stupid, hacky, pointless approach when it's called copy-and-patch ;)

but still like to see credit where it's due

I wonder if they're truly unaware of one another and developed in parallel or not. Hmmm