>> As such, the property of being verifiable is irrelevant. > > No. It's a fundamental property of BPF. > If it's not verifiable it's not BPF. Sure. > It's not xBPF either. Heh, beg to differ :) > Please call it something else and don't confuse people that your ISA > has any overlap with BPF. It doesn't. It's not verifiable. Nonsense. xBPF has as much overlap with BPF as it can have: around 99%. The purpose of having the e_flag is to avoid confusion, not to increase it. xBPF objects are mainly used to test the GCC BPF backend (and other purposes we have in mind, like ease the debugging of BPF programs) but we want to eliminate the chance of these objects to be confused with legit BPF files, and used as such.
