Re: [PATCH 2/1] c++/modules: Handle gnu_inline, again [PR119154]

2025-04-05 Thread Jason Merrill
On 3/22/25 8:37 AM, Nathaniel Shead wrote: On Mon, Mar 17, 2025 at 09:42:13AM -0400, Jason Merrill wrote: On 3/14/25 9:28 AM, Nathaniel Shead wrote: Bootstrapped and regtested on x86_64-pc-linux-gnu, OK for trunk? Alternatively, could still mark gnu_inline functions as non-vague, we just need

Re: [PATCH 2/1] c++/modules: Handle gnu_inline, again [PR119154]

2025-03-22 Thread Nathaniel Shead
On Mon, Mar 17, 2025 at 09:42:13AM -0400, Jason Merrill wrote: > On 3/14/25 9:28 AM, Nathaniel Shead wrote: > > Bootstrapped and regtested on x86_64-pc-linux-gnu, OK for trunk? > > > > Alternatively, could still mark gnu_inline functions as non-vague, we > > just need to do so more aggressively; b

Re: [PATCH 2/1] c++/modules: Handle gnu_inline, again [PR119154]

2025-03-17 Thread Jason Merrill
On 3/14/25 9:28 AM, Nathaniel Shead wrote: Bootstrapped and regtested on x86_64-pc-linux-gnu, OK for trunk? Alternatively, could still mark gnu_inline functions as non-vague, we just need to do so more aggressively; but given this is specifically to solve a modules issue I felt may as well keep

[PATCH 2/1] c++/modules: Handle gnu_inline, again [PR119154]

2025-03-15 Thread Nathaniel Shead
Bootstrapped and regtested on x86_64-pc-linux-gnu, OK for trunk? Alternatively, could still mark gnu_inline functions as non-vague, we just need to do so more aggressively; but given this is specifically to solve a modules issue I felt may as well keep it confined to there given your previous comm