public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sezeroz at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/39064] libiberty md5.h needs uintptr_t Date: Sun, 01 Feb 2009 16:57:00 -0000 [thread overview] Message-ID: <20090201165723.11950.qmail@sourceware.org> (raw) In-Reply-To: <bug-39064-17247@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from sezeroz at gmail dot com 2009-02-01 16:57 ------- Created an attachment (id=17223) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17223&action=view) libiberty md5.h win64 patch -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39064
next prev parent reply other threads:[~2009-02-01 16:57 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-02-01 16:56 [Bug target/39064] New: " sezeroz at gmail dot com 2009-02-01 16:57 ` sezeroz at gmail dot com [this message] 2009-02-21 9:54 ` [Bug target/39064] " ktietz at gcc dot gnu dot org 2009-03-14 15:47 ` nightstrike at gmail dot com 2009-09-03 10:10 ` sezeroz at gmail dot com [not found] <bug-39064-4@http.gcc.gnu.org/bugzilla/> 2010-11-17 13:14 ` nightstrike at gmail dot com 2013-01-30 16:51 ` ktietz at gcc dot gnu.org 2013-01-30 16:57 ` ktietz at gcc dot gnu.org 2013-01-30 16:58 ` ktietz at gcc dot gnu.org 2013-01-30 17:00 ` 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=20090201165723.11950.qmail@sourceware.org \ --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).