Hi,
On Tue Mar 25, 2025 at 8:33 PM CET, Simon Martin wrote:
> Hi,
>
> On Tue Mar 25, 2025 at 6:52 PM CET, Jason Merrill wrote:
>> On 3/25/25 1:50 PM, Marek Polacek wrote:
>>> On Tue, Mar 25, 2025 at 05:18:23PM +, Simon Martin wrote:
We've been miscompiling the following since r0-51314-gd6
We've been miscompiling the following since r0-51314-gd6b4ea8592e338 (I
did not go compile something that old, and identified this change via
git blame, so might be wrong)
=== cut here ===
struct Foo { int x; };
Foo& get (Foo &v) { return v; }
void bar () {
Foo v; v.x = 1;
(true ? get (v) : ge
On 3/25/25 1:50 PM, Marek Polacek wrote:
On Tue, Mar 25, 2025 at 05:18:23PM +, Simon Martin wrote:
We've been miscompiling the following since r0-51314-gd6b4ea8592e338 (I
did not go compile something that old, and identified this change via
git blame, so might be wrong)
=== cut here ===
str
Hi,
On Tue Mar 25, 2025 at 6:52 PM CET, Jason Merrill wrote:
> On 3/25/25 1:50 PM, Marek Polacek wrote:
>> On Tue, Mar 25, 2025 at 05:18:23PM +, Simon Martin wrote:
>>> We've been miscompiling the following since r0-51314-gd6b4ea8592e338 (I
>>> did not go compile something that old, and identi
On Tue, Mar 25, 2025 at 05:18:23PM +, Simon Martin wrote:
> We've been miscompiling the following since r0-51314-gd6b4ea8592e338 (I
> did not go compile something that old, and identified this change via
> git blame, so might be wrong)
>
> === cut here ===
> struct Foo { int x; };
> Foo& get (
On 3/25/25 1:18 PM, Simon Martin wrote:
We've been miscompiling the following since r0-51314-gd6b4ea8592e338 (I
did not go compile something that old, and identified this change via
git blame, so might be wrong)
=== cut here ===
struct Foo { int x; };
Foo& get (Foo &v) { return v; }
void bar ()
