public inbox for
 help / color / mirror / Atom feed
* Re: Question about why GCC produces the wrong-code bug
       [not found] <>
@ 2022-09-17 21:02 ` Jakub Jelinek
  0 siblings, 0 replies; only message in thread
From: Jakub Jelinek @ 2022-09-17 21:02 UTC (permalink / raw)
  To: Haoxin Tu; +Cc: GCC Mailing List

On Sat, Sep 17, 2022 at 11:18:56PM +0800, Haoxin Tu via Gcc wrote:
> Dear developers,
> May I seek your help with some understanding of why GCC produces the
> wrong-code bug? I understand that such a bug can only be reproduced in an
> old GCC version, but I still want to know why GCC made mistake here.
> The bug-revealing code makes GCC-4.7.0 produce miscompiled code under the
> -O3 option.
> $gcc-4.7.0 -O1 s.c -o s1; ./s1
> Aborted (core dumped)
> $gcc-4.7.0 -O3 s.c -o s2; ./s2

From what I can see, this has been introduced in
aka PR49094 fix and got fixed in
aka PR54634 fix.  But if you want to know more, you need to figure it out
yourself, nobody is going to spend time on no longer supported 10 years old


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2022-09-17 21:02 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <>
2022-09-17 21:02 ` Question about why GCC produces the wrong-code bug Jakub Jelinek

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).