public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamessan at jamessan dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/95676] New: [armhf] g++ mis-compiles code at -O1 or above
Date: Mon, 15 Jun 2020 04:33:17 +0000 [thread overview]
Message-ID: <bug-95676-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95676
Bug ID: 95676
Summary: [armhf] g++ mis-compiles code at -O1 or above
Product: gcc
Version: 9.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: jamessan at jamessan dot com
Target Milestone: ---
Created attachment 48730
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48730&action=edit
Reduced test case
After uploading msgpack-c 3.3.0 to Debian, the armhf build failed due to a
specific test failing. I originally reported this to msgpack-c's upstream:
https://github.com/msgpack/msgpack-c/issues/881
However, after testing on Debian's porterbox, it seems to be a GCC issue. The
issue does not reproduce when compiled with -O0 but does with -O1 or higher.
Similarly, changing the line that was failing from using googletest's
"EXPECT_TRUE(foo == bar);" to "EXPECT_EQ(foo, bar);" caused the test to pass.
I was able to use creduce to produce the attached file, test.cpp, which
exhibits the problem. The final assignment in main (cd = ce.aq<ba::z::bw>() ==
g;) should always evaluate to true.
next reply other threads:[~2020-06-15 4:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 4:33 jamessan at jamessan dot com [this message]
2020-06-15 13:00 ` [Bug target/95676] " rearnsha at gcc dot gnu.org
2020-06-16 0:49 ` jamessan at jamessan dot com
2020-06-23 4:45 ` jamessan at jamessan dot com
2020-06-23 14:34 ` acoplan at gcc dot gnu.org
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=bug-95676-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).