public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "markus at oberhumer dot com" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/362] New: sysdeps/generic/bits/types.h fix for compilers without __GLIBC_HAVE_LONG_LONG
Date: Wed, 01 Sep 2004 13:47:00 -0000 [thread overview]
Message-ID: <20040901134731.362.markus@oberhumer.com> (raw)
This small patch fixes bits/types.h for compilers without __GLIBC_HAVE_LONG_LONG.
Index: sysdeps/generic/bits/types.h
===================================================================
RCS file: /cvs/glibc/libc/sysdeps/generic/bits/types.h,v
retrieving revision 1.22
diff -u -r1.22 types.h
--- sysdeps/generic/bits/types.h 9 Sep 2003 00:04:25 -0000 1.22
+++ sysdeps/generic/bits/types.h 1 Sep 2004 13:44:03 -0000
@@ -106,8 +106,8 @@
#define __SLONGWORD_TYPE long int
#define __ULONGWORD_TYPE unsigned long int
#if __WORDSIZE == 32
-# define __SQUAD_TYPE long long int
-# define __UQUAD_TYPE unsigned long long int
+# define __SQUAD_TYPE __quad_t
+# define __UQUAD_TYPE __u_quad_t
# define __SWORD_TYPE int
# define __UWORD_TYPE unsigned int
# define __SLONG32_TYPE long int
--
Summary: sysdeps/generic/bits/types.h fix for compilers without
__GLIBC_HAVE_LONG_LONG
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: libc
AssignedTo: gotom at debian dot or dot jp
ReportedBy: markus at oberhumer dot com
CC: glibc-bugs at sources dot redhat dot com
http://sources.redhat.com/bugzilla/show_bug.cgi?id=362
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2004-09-01 13:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-01 13:47 markus at oberhumer dot com [this message]
2004-09-26 8:48 ` [Bug libc/362] " drepper at redhat 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=20040901134731.362.markus@oberhumer.com \
--to=sourceware-bugzilla@sources.redhat.com \
--cc=glibc-bugs@sources.redhat.com \
/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).