GNU bug report logs - #40671
[DOC] modify literal objects

Previous Next

Full log

Message #189 received at 40671 <at> debbugs.gnu.org (full text, mbox):

From: Dmitry Gutov <dgutov <at> yandex.ru>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: ke.vigouroux <at> laposte.net, eggert <at> cs.ucla.edu, 40671 <at> debbugs.gnu.org,
 michael_heerdegen <at> web.de, mattiase <at> acm.org, rms <at> gnu.org
Subject: Re: bug#40671: [DOC] modify literal objects
Date: Sun, 26 Apr 2020 21:32:45 +0300

On 26.04.2020 21:14, Eli Zaretskii wrote:
>> Cc: ke.vigouroux <at> laposte.net, eggert <at> cs.ucla.edu, 40671 <at> debbugs.gnu.org,
>>   michael_heerdegen <at> web.de, mattiase <at> acm.org, rms <at> gnu.org
>> From: Dmitry Gutov <dgutov <at> yandex.ru>
>> Date: Sun, 26 Apr 2020 20:39:38 +0300
>>
>> int main (void) {
>>     return ((int(*) (int))"abc")(1);
>> }
>>
>> It will blow up at runtime, of course.
> 
> But the previous program will not necessarily blow up at runtime.

"not necessarily" is a damnably low qualifier.

My point is, that program is using the same instrument as this one, 
which *will* blow up at runtime. And the instrument is "making the 
compiler shut up".

Previous Next

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