public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/39065] libiberty hashtab.c:hash_pointer() needs intptr_t
Date: Thu, 03 Sep 2009 16:46:00 -0000	[thread overview]
Message-ID: <20090903164629.20438.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39065-17247@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from hjl at gcc dot gnu dot org  2009-09-03 16:46 -------
Subject: Bug 39065

Author: hjl
Date: Thu Sep  3 16:46:00 2009
New Revision: 151386

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=151386
Log:
2009-09-03  Ozkan Sezer  <sezeroz@gmail.com>

        PR target/39065
        * configure.ac: Also check for intptr_t.
        * config.h.in: Regenerated.
        * configure: Regenerated.
        * hashtab.c (hash_pointer): Cast the pointer argument to intptr_t
        instead of of long.

Modified:
    trunk/libiberty/ChangeLog
    trunk/libiberty/config.in
    trunk/libiberty/configure
    trunk/libiberty/configure.ac
    trunk/libiberty/hashtab.c


-- 


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


  parent reply	other threads:[~2009-09-03 16:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-01 16:59 [Bug target/39065] New: " sezeroz at gmail dot com
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 [this message]
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=20090903164629.20438.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: 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).