public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "markus at oberhumer dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/18745] New: compile fix for gcc/include/md5.h
Date: Tue, 30 Nov 2004 21:03:00 -0000 [thread overview]
Message-ID: <20041130210257.18745.markus@oberhumer.com> (raw)
gcc/include/md5.h currently does not compile under ILP64.
This tiny patch will fix this:
--- md5.h 14 Mar 2001 19:44:38 -0000 1.3
+++ md5.h 30 Nov 2004 20:59:32 -0000
@@ -58,9 +58,13 @@
# if LONG_MAX == INT_MAX_32_BITS
typedef unsigned long md5_uint32;
# else
- /* The following line is intended to evoke an error.
- Using #error is not portable enough. */
- "Cannot determine unsigned 32-bit data type."
+# if defined(__GNUC__) && (__GNUC__ >= 3) && (__INT_MAX__ > 2147483647)
+ typedef unsigned int md5_uint32 __attribute__ ((__mode__ (__SI__)));
+# else
+ /* The following line is intended to evoke an error.
+ Using #error is not portable enough. */
+ "Cannot determine unsigned 32-bit data type."
+# endif
# endif
# endif
# endif
--
Summary: compile fix for gcc/include/md5.h
Product: gcc
Version: 3.4.3
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bootstrap
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: markus at oberhumer dot com
CC: gcc-bugs at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18745
next reply other threads:[~2004-11-30 21:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-30 21:03 markus at oberhumer dot com [this message]
2004-11-30 21:04 ` [Bug bootstrap/18745] " markus at oberhumer dot com
2004-11-30 21:07 ` pinskia at gcc dot gnu dot org
2004-11-30 21:08 ` pinskia at gcc dot gnu dot org
2004-11-30 21:18 ` markus at oberhumer 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=20041130210257.18745.markus@oberhumer.com \
--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).