public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Test: {mingw64-{i686,x86_64}-,}gcc-11.1.0-0.1
Date: Thu, 13 May 2021 10:57:50 +0200	[thread overview]
Message-ID: <29a53ee2-cac3-6815-792d-36f96be47bd1@towo.net> (raw)
In-Reply-To: <87mtszzsvd.fsf@Rainer.invalid>


Am 12.05.2021 um 20:53 schrieb Achim Gratz:
> Thomas Wolff writes:
>> Am 10.05.2021 um 21:13 schrieb Achim Gratz:
>>> The native and mingw-w64 cross compilers have been updated for both
>>> architectures to the latest upstream release version:
>>>
>>>    gcc-11.1.0-0.1
>> Are there any known problems with gcc 11? My program crashes if
>> compiled with gcc -O2; gcc -O1 works, gcc 10 also works.
> None that I'd know of, especially given that very vague symptoms.  While
> I guess it's possible that there's a bug in the optimizer, I'd first
> attempt to rule out undefined behaviour in the program being compiled.
The crash vanishes after removing a few lines from a conditional (if 
block) where the condition is false.
This smells like wrong calculation of a relative jump (Intel "short 
jump") by the optimizer.

>
>
> Regards,
> Achim.


  reply	other threads:[~2021-05-13  8:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10 19:13 Achim Gratz
2021-05-12  9:14 ` Thomas Wolff
2021-05-12 10:42   ` Jonathan Yong
2021-05-12 18:30     ` Thomas Wolff
2021-05-13  1:41       ` Brian Inglis
2021-05-13  2:22         ` Thomas Wolff
2021-05-12 18:53   ` Achim Gratz
2021-05-13  8:57     ` Thomas Wolff [this message]
2021-05-13 19:33       ` Hans-Bernhard Bröker
2021-05-13 21:57         ` Thomas Wolff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=29a53ee2-cac3-6815-792d-36f96be47bd1@towo.net \
    --to=towo@towo.net \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).