[PATCH v4 16/20] Refactor FMV frontend conflict and merging logic and hooks.

2025-05-28 Thread Alfie Richards
This change refactors FMV handling in the frontend to allows greater reasoning about versions in shared code. This is needed for allowing target_clones and target_versions to be used together in a function set, as there is then two distinct concerns when encountering two declarations that previous

Re: [PATCH v4 16/20] Refactor FMV frontend conflict and merging logic and hooks.

2025-05-20 Thread Alfie Richards
On 20/05/2025 03:28, Jason Merrill wrote: On 4/15/25 6:31 AM, Alfie Richards wrote: This change refactors FMV handling in the frontend to allows greater reasoning about versions in shared code. Looking at the cp/ changes: diff --git a/gcc/cp/class.cc b/gcc/cp/class.cc index c28d9e5b3ab..4f19

Re: [PATCH v4 16/20] Refactor FMV frontend conflict and merging logic and hooks.

2025-05-19 Thread Jason Merrill
On 4/15/25 6:31 AM, Alfie Richards wrote: This change refactors FMV handling in the frontend to allows greater reasoning about versions in shared code. Looking at the cp/ changes: diff --git a/gcc/cp/class.cc b/gcc/cp/class.cc index c28d9e5b3ab..4f195ae06cd 100644 --- a/gcc/cp/class.cc +++ b/

[PATCH v4 16/20] Refactor FMV frontend conflict and merging logic and hooks.

2025-04-15 Thread Alfie Richards
This change refactors FMV handling in the frontend to allows greater reasoning about versions in shared code. This is needed for allowing target_clones and target_versions to be used together in a function set, as there is then two distinct concerns when encountering two declarations that previous