From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Test: {mingw64-{i686,x86_64}-,}gcc-11.1.0-0.1
Date: Thu, 13 May 2021 21:33:19 +0200 [thread overview]
Message-ID: <5d911b7f-70c6-01f5-a353-d8735be46ecd@t-online.de> (raw)
In-Reply-To: <29a53ee2-cac3-6815-792d-36f96be47bd1@towo.net>
Am 13.05.2021 um 10:57 schrieb Thomas Wolff:
> The crash vanishes after removing a few lines from a conditional (if
> block) where the condition is false.
A conditions that's always false, or one that's false during the
execution of a particular test case?
> This smells like wrong calculation of a relative jump (Intel "short
> jump") by the optimizer.
If it were that simple, the problematic change should stand out like the
proverbial sore thumb when comparing assembly listings of the two cases.
Does it?
next prev parent reply other threads:[~2021-05-13 19:33 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
2021-05-13 19:33 ` Hans-Bernhard Bröker [this message]
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=5d911b7f-70c6-01f5-a353-d8735be46ecd@t-online.de \
--to=hbbroeker@t-online.de \
--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).