Re: [PATCH] c++: Fix checking assert upon invalid class definition [PR116740]

2025-03-04 Thread Jason Merrill
On 2/18/25 8:00 AM, Simon Martin wrote: A checking assert triggers upon the following invalid code since GCC 11: === cut here === class { a (struct b; } struct b === cut here === The problem is that during error recovery, we call set_identifier_type_value_with_scope for B in the global namespac

[PING] [PATCH] c++: Fix checking assert upon invalid class definition [PR116740]

2025-03-03 Thread Simon Martin
Hi, On 18 Feb 2025, at 14:00, Simon Martin wrote: > A checking assert triggers upon the following invalid code since > GCC 11: > > === cut here === > class { a (struct b; > } struct b > === cut here === > > The problem is that during error recovery, we call > set_identifier_type_value_with_scope

[PATCH] c++: Fix checking assert upon invalid class definition [PR116740]

2025-02-18 Thread Simon Martin
A checking assert triggers upon the following invalid code since GCC 11: === cut here === class { a (struct b; } struct b === cut here === The problem is that during error recovery, we call set_identifier_type_value_with_scope for B in the global namespace, and the checking assert added via r11-7