GNU bug report logs - #76559
31.0.50; [-O3 + PGTK] Crash when 'copying as kill'/'killing word'

Previous Next

Full log

View this message in rfc822 format

From: Po Lu <luangruo <at> yahoo.com>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: Pip Cet <pipcet <at> protonmail.com>, iura.mail <at> gmail.com, Stefan Kangas <stefankangas <at> gmail.com>, michael.albinus <at> gmx.de, Eli Zaretskii <eliz <at> gnu.org>, 76559 <at> debbugs.gnu.org, marian.iurie <at> gmail.com
Subject: bug#76559: 31.0.50; [-O3 + PGTK] Crash when 'copying as kill'/'killing word'
Date: Sun, 02 Mar 2025 16:07:41 +0800

Paul Eggert <eggert <at> cs.ucla.edu> writes:

> On 2025-03-01 21:10, Po Lu wrote:
>>> I don't see why that assumption would cause GCC to generate the wrong
>>> code here, as no single thread of execution would have two such
>>> accesses.
>> It doesn't take control flow into account, but rather _every statement
>> operand_ in the current procedure that addresses an aggregate declared
>> in the same procedure.
>
> In that case it's a GCC bug, right? Since GCC promises that one can do
> union punning.

Yes, that's what I was getting at.  I even proposed a fix.  But the GCC
list has lately been infused with a series of threads proposing new
obstacles to engaging with its developers (search "Sourceware
infrastructure plans"), and I'm not interested...

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.