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] libibiberty's md5.c builds with warnings with 4.7 and trunk Date: Mon, 28 May 2012 07:26:00 -0000 [thread overview] Message-ID: <bug-53285-4-VdbCBZQLVg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53285-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53285 --- Comment #2 from Matthias Klose <doko at gcc dot gnu.org> 2012-05-28 06:42:37 UTC --- the patch is incomplete. the patch from glibc is found at http://sourceware.org/git/?p=glibc.git;a=patch;h=7dc6bd90c569c49807462b0740b18e32fab4d8b7 using anonymous unions which cannot be used for stage1. The original patch is http://sourceware.org/ml/libc-alpha/2011-07/msg00085.html A third approach from gnulib is pointed out in http://sourceware.org/ml/libc-alpha/2011-07/msg00093.html
next prev parent reply other threads:[~2012-05-28 6:42 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-08 22:31 [Bug other/53285] New: " doko at gcc dot gnu.org 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 [this message] 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-VdbCBZQLVg@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: linkBe 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).