Dmitry Vyukov

Dup of #2297?

Do you use bazel or cmake build? I am not an expert on all open-source absl build modes. Is it possible to add a test for this? I see this...

> It would be functionally equivalent to the patch I posted above, which I already tested successfully. If I read your first patch correctly, it effectively undoes the optimization, so...

Does this build include inconsistent NDEBUG defines (as @derekmauro mentioned here https://github.com/abseil/abseil-cpp/issues/1624#issuecomment-1967655080)?

I still think we should use executor's remove_dir as part of setup procedure to delete these files. We are playing whack-a-mole and duplicating code in shell.

We can do it after booting the machine roughly at the same time the current removal hack runs. Executor setup already runs after booting the machine, and the cleanup looks...

"syz-executor setup" is run in the same dir where all fuzzing syz-executor processes are started. The temp dir for syz-executor is ".", so implicitly it knows it. I think "setup"...

Will it be simpler if we lower this to a varlen union with a value and a void field (similar to the current opt template)? Then we can just select...

I meant A. Syntax and internal representation don't need to match. We already do a number of such transformations in the compiler. > For prog, it will be union, so...

> For structs, we used to refer to the whole struct as parent, so parent:field must logically mean a field in the same structure, just as if parent: was not...