Re: [PATCH 5/5] passes: Remove limit on the number of params

2024-10-14 Thread Eric Gallager
On Mon, Oct 14, 2024 at 10:17 AM Andrew Pinski wrote: > > On Mon, Oct 14, 2024 at 6:10 AM Richard Biener > wrote: > > > > On Mon, Oct 14, 2024 at 4:32 AM Andrew Pinski > > wrote: > > > > > > Having a limit of 2 params for NEXT_PASS was just done because I didn't > > > think there was > > > a w

Re: [PATCH 5/5] passes: Remove limit on the number of params

2024-10-14 Thread Andrew Pinski
On Mon, Oct 14, 2024 at 6:10 AM Richard Biener wrote: > > On Mon, Oct 14, 2024 at 4:32 AM Andrew Pinski > wrote: > > > > Having a limit of 2 params for NEXT_PASS was just done because I didn't > > think there was > > a way to handle arbitrary number of params. But I found that we can handle >

Re: [PATCH 5/5] passes: Remove limit on the number of params

2024-10-14 Thread Richard Biener
On Mon, Oct 14, 2024 at 4:32 AM Andrew Pinski wrote: > > Having a limit of 2 params for NEXT_PASS was just done because I didn't think > there was > a way to handle arbitrary number of params. But I found that we can handle > this > via a static const variable array (constexpr so we know it is t

[PATCH 5/5] passes: Remove limit on the number of params

2024-10-13 Thread Andrew Pinski
Having a limit of 2 params for NEXT_PASS was just done because I didn't think there was a way to handle arbitrary number of params. But I found that we can handle this via a static const variable array (constexpr so we know it is true or false at compile time) and just loop over the array. Note