public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/53285] New: libibiberty's md5.c builds with warnings with 4.7 and trunk
Date: Tue, 08 May 2012 22:31:00 -0000 [thread overview]
Message-ID: <bug-53285-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53285
Bug #: 53285
Summary: libibiberty's md5.c builds with warnings with 4.7 and
trunk
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: doko@gcc.gnu.org
when libibiberty's md5.c is built using 4.7 or trunk on x86-linux, the
following warning is emitted:
md5.c: In function 'md5_finish_ctx':
md5.c:119:2: error: dereferencing type-punned pointer will break
strict-aliasing rules [-Werror=strict-aliasing]
*(md5_uint32 *) & ctx->buffer[bytes + pad] = SWAP (ctx->total[0] << 3);
^
md5.c:120:2: error: dereferencing type-punned pointer will break
strict-aliasing rules [-Werror=strict-aliasing]
*(md5_uint32 *) & ctx->buffer[bytes + pad + 4] =
^
afaics this is the only warning emitted when building libiberty when built with
4.7 or trunk.
next reply other threads:[~2012-05-08 22:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 22:31 doko at gcc dot gnu.org [this message]
2012-05-28 5:11 ` [Bug other/53285] " doko at gcc dot gnu.org
2012-05-28 7:26 ` doko at gcc dot gnu.org
2013-01-31 8:14 ` ktietz at gcc dot gnu.org
2013-01-31 8:22 ` ktietz 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-53285-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).