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/39065]  New: libiberty hashtab.c:hash_pointer() needs intptr_t
Date: Sun, 01 Feb 2009 16:59:00 -0000	[thread overview]
Message-ID: <bug-39065-17247@http.gcc.gnu.org/bugzilla/> (raw)

in function hash_pointer(), libiberty/hashtab.c casts its pointer argument
to long, probably with the assumption that long is 64 bits on all 64 bit
systems, which isn't true for win64. it must cast to intptr_t, instead.
here is the warning:
../../../gcc-svn/libiberty/hashtab.c: In function 'hash_pointer':
../../../gcc-svn/libiberty/hashtab.c:199: warning: cast from pointer to integer
of different size

(the patch should also be applied to binutils and gdb, or whoever else uses
libiberty)


-- 
           Summary: libiberty hashtab.c:hash_pointer() needs intptr_t
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Severity: trivial
          Priority: P3
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: sezeroz at gmail dot com
GCC target triplet: x86_64-pc-mingw32


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39065


             reply	other threads:[~2009-02-01 16:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-01 16:59 sezeroz at gmail dot com [this message]
2009-02-01 17:00 ` [Bug target/39065] " sezeroz at gmail dot com
2009-02-02 21:52 ` dj at redhat dot com
2009-02-02 22:59 ` sezeroz at gmail dot com
2009-02-21  8:06 ` sezeroz at gmail dot com
2009-02-21  9:55 ` ktietz at gcc dot gnu dot org
2009-03-14 15:58 ` nightstrike at gmail dot com
2009-09-03 16:46 ` hjl at gcc dot gnu dot org
2009-09-04  6:26 ` sezeroz at gmail dot com
2009-09-04 14:33 ` hjl at gcc dot gnu dot 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-39065-17247@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: 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).