From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Roland Denis <denis@math.univ-lyon1.fr>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Kind of undefined behavior (or bug?) with GCC 10.1
Date: Tue, 16 Jun 2020 13:59:15 +0100 [thread overview]
Message-ID: <CAH6eHdQ8WF0LVbDQQ-ZQCh29sNO3km-zyCkfX2P0950OZgoKmA@mail.gmail.com> (raw)
In-Reply-To: <e4cfa51e-2512-3fbf-7238-6dde4067a3cc@math.univ-lyon1.fr>
On Tue, 16 Jun 2020 at 12:58, Roland Denis wrote:
> Am I missing something important or does that look like a GCC bug ?
It's a bug. It started with https://gcc.gnu.org/r271510 and was fixed
in the master branch by https://gcc.gnu.org/r11-963 which was
addressing https://gcc.gnu.org/PR95493 which is a different bug.
> PS: result is correct with trunk version of GCC in godbolt, does that
> mean it is an already solved bug?
Looks like it, but I've added a comment to PR 95493 so that it can be
investigated and we can be sure your problem is really fixed.
next prev parent reply other threads:[~2020-06-16 12:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 11:57 Roland Denis
2020-06-16 12:59 ` Jonathan Wakely [this message]
2020-06-16 13:34 ` Roland Denis
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=CAH6eHdQ8WF0LVbDQQ-ZQCh29sNO3km-zyCkfX2P0950OZgoKmA@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=denis@math.univ-lyon1.fr \
--cc=gcc-help@gcc.gnu.org \
/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).