public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: theller@python.org To: gcc-gnats@gcc.gnu.org Subject: other/9398: Bug in ffi.h.in header file Date: Wed, 22 Jan 2003 08:36:00 -0000 [thread overview] Message-ID: <20030122082809.5118.qmail@sources.redhat.com> (raw) >Number: 9398 >Category: other >Synopsis: Bug in ffi.h.in header file >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Wed Jan 22 08:36:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: theller@python.org >Release: Current CVS (2003-01-22) >Organization: >Environment: >Description: There's a bug in gcc/libffi/include/ffi.h.in. ffi_type_ulong and ffi_type_slong over redefined to wrong values here (they are defined before when SIZEOF_LONG == 4): #if SIZEOF_LONG_LONG == 8 #define UINT64 unsigned long long #define SINT64 long long #define ffi_type_ulong ffi_type_uint64 #define ffi_type_slong ffi_type_sint64 #endif >How-To-Repeat: >Fix: IMO it should read instead: #if SIZEOF_LONG_LONG == 8 #define UINT64 unsigned long long #define SINT64 long long #define ffi_type_ulonglong ffi_type_uint64 #define ffi_type_slonglong ffi_type_sint64 #endif >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-01-22 8:36 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-22 8:36 theller [this message] 2003-01-23 19:16 Thomas Heller
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=20030122082809.5118.qmail@sources.redhat.com \ --to=theller@python.org \ --cc=gcc-gnats@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).