> On 8/5/22 05:41, Jose E. Marchesi via Gcc-patches wrote:
>> [Changes from V1:
>> - Added a test.]
>>
>> It is common for C BPF programs to use variables that are implicitly
>> set by the BPF loader and run-time. It is also necessary for these
>> variables to be stored in read-only storage so t
> On Sep 27, 2022, at 8:51 PM, Jeff Law via Gcc-patches
> wrote:
>
>
> On 8/5/22 05:41, Jose E. Marchesi via Gcc-patches wrote:
>> [Changes from V1:
>> - Added a test.]
>>
>> It is common for C BPF programs to use variables that are implicitly
>> set by the BPF loader and run-time. It is a
On 8/5/22 05:41, Jose E. Marchesi via Gcc-patches wrote:
[Changes from V1:
- Added a test.]
It is common for C BPF programs to use variables that are implicitly
set by the BPF loader and run-time. It is also necessary for these
variables to be stored in read-only storage so the BPF verifier
r
ping
> [Changes from V1:
> - Added a test.]
>
> It is common for C BPF programs to use variables that are implicitly
> set by the BPF loader and run-time. It is also necessary for these
> variables to be stored in read-only storage so the BPF verifier
> recognizes them as such. This leads to d
