Hi Alex,
Yeah I assumed it was an older version because the errors triggered by
clang11 stop the compilation.
I checked again and for oss-fuzz, you disable failing on warnings.
So again, these patches are not directly connected to CFI and therefore
could land independently.
On 11/6/2020 9:58
On 201106 0835, Daniele Buono wrote:
> Hi Cornelia,
>
> I don't have a real preference either way.
>
> So if it is acceptable to have the clang11+ patches separated and
> handled by the maintainers for the proper subsystem, I'd say whatever
> the maintainers prefer.
>
> In my opinion, the patche
Hi Cornelia,
I don't have a real preference either way.
So if it is acceptable to have the clang11+ patches separated and
handled by the maintainers for the proper subsystem, I'd say whatever
the maintainers prefer.
In my opinion, the patches for clang11+ support may be merged
separately.
I'm
On Thu, 5 Nov 2020 17:18:56 -0500
Daniele Buono wrote:
> This patch adds supports for Control-Flow Integrity checks
> on indirect function calls.
>
> Requires the use of clang, and link-time optimizations
>
> Changes in v3:
>
> - clang 11+ warnings are now handled directly at the source,
> in
This patch adds supports for Control-Flow Integrity checks
on indirect function calls.
Requires the use of clang, and link-time optimizations
Changes in v3:
- clang 11+ warnings are now handled directly at the source,
instead of disabling specific warnings for the whole code.
Some more work may
