public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/63645] Incorrect code generation
Date: Sat, 25 Oct 2014 21:37:00 -0000 [thread overview]
Message-ID: <bug-63645-4-nP1xAY9MDh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63645-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63645
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This:
expr->oper == GNM_EXPR_OP_FUNCALL &&
expr->func.argc == 1
is being combined into:
D.2319_2 = BIT_FIELD_REF <*expr_1, 64, 0>;
D.2320_3 = D.2319_2 & 18446744069414584575;
D.2320_3 == 4294967297
Which is correct and I think is valid.
Valgrind does not realize the part of expr will not match part of the
and/equals so it complains. Basically a bug in valgrind for not tracking
uninitialized bits correctly.
The solution to asan message was provided in comment #4.
next prev parent reply other threads:[~2014-10-25 21:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 20:15 [Bug c/63645] New: " terra at gnome dot org
2014-10-25 20:18 ` [Bug c/63645] " terra at gnome dot org
2014-10-25 20:22 ` pinskia at gcc dot gnu.org
2014-10-25 20:22 ` terra at gnome dot org
2014-10-25 21:19 ` trippels at gcc dot gnu.org
2014-10-25 21:30 ` terra at gnome dot org
2014-10-25 21:37 ` pinskia at gcc dot gnu.org [this message]
2014-10-25 21:52 ` trippels at gcc dot gnu.org
2014-10-26 1:35 ` mikpelinux at gmail dot com
2014-10-27 3:48 ` terra at gnome dot org
2014-10-27 7:52 ` trippels at gcc dot gnu.org
2014-10-27 9:30 ` jakub at gcc dot gnu.org
2014-10-27 11:41 ` terra at gnome dot org
2014-10-27 14:59 ` trippels at gcc dot gnu.org
2014-10-27 15:31 ` terra at gnome dot org
2014-10-27 15:40 ` terra at gnome dot org
2014-10-27 15:43 ` joseph at codesourcery dot com
2014-10-27 16:25 ` jakub at gcc dot gnu.org
2014-10-27 16:50 ` schwab@linux-m68k.org
2014-10-27 17:30 ` terra at gnome dot org
2014-10-27 18:29 ` joseph at codesourcery dot com
2014-10-27 18:46 ` joseph at codesourcery dot com
2014-10-28 10:14 ` mikpelinux at gmail dot com
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-63645-4-nP1xAY9MDh@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).