public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kai Tietz <ktietz70@googlemail.com>
To: Dave Korn <dave.korn.cygwin@googlemail.com>
Cc: Andrew Pinski <pinskia@gmail.com>, Andrew Haley <aph@redhat.com>,
	gcc@gcc.gnu.org, java@gcc.gnu.org
Subject: Re: RFA: libjava seems to miss some files for win32
Date: Sat, 18 Jul 2009 19:27:00 -0000	[thread overview]
Message-ID: <90baa01f0907181227x699647a3nd1a60b88888b6a7b@mail.gmail.com> (raw)
In-Reply-To: <4A622420.40803@gmail.com>

2009/7/18 Dave Korn <dave.korn.cygwin@googlemail.com>:
> Andrew Pinski wrote:
>> On Sat, Jul 18, 2009 at 12:08 PM, Andrew Haley<aph@redhat.com> wrote:
>>> Don't use uintptr_t, use unsigned int __attribute__((mode(PTR)).  This
>>> is built-in to gcc, not a dependency on the host libc which might not
>>> be c99..'
>>
>> Except uintptr_t is required to be provided by a non hosted compiler like GCC.
>
>  Come to think of it, we should use the __UINTPTR_TYPE__ thingy provided by
> jsm's recent stdint patch, shouldn't we?
>
>    cheers,
>      DaveK
>

Well, this sounds good. I wasn't aware that __UINTPTR_TYPE__ is
present. I just was aware of the SIZE, and PTRDIFF builtin macros,
which aren't useful here for all targets.
Maybe a __ULONGPTR_TYPE__ should be added as internal macro, too.
Because sometimes the widest scalar type between MAX(sizeof(long),
sizeof(void *)) is necessary, too. E.g. in libiberty there are such
cases I remember.


Cheers,
Kai

-- 
|  (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination

  reply	other threads:[~2009-07-18 19:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <90baa01f0907180506h1a58152du5d45d66628043ad9@mail.gmail.com>
2009-07-18 13:53 ` Dave Korn
2009-07-18 16:01   ` Kai Tietz
2009-07-18 17:09     ` Dave Korn
2009-07-18 17:27       ` Kai Tietz
2009-07-18 18:15         ` Dave Korn
2009-07-18 19:09           ` Andrew Haley
2009-07-18 19:19             ` Andrew Pinski
2009-07-18 19:23               ` Dave Korn
2009-07-18 19:27                 ` Kai Tietz [this message]
2009-07-18 19:23               ` Kai Tietz
2009-07-18 19:29                 ` Andrew Pinski
2009-07-19 11:13                   ` Kai Tietz
2009-07-19 13:16                     ` Dave Korn
2009-07-19 13:31                       ` Kai Tietz
2009-07-19 13:45                         ` Dave Korn
2009-07-19 13:55                           ` Kai Tietz
2009-07-19 14:39                             ` Dave Korn
2009-07-19 15:23                       ` Andrew Haley
2009-07-19 17:07                         ` Dave Korn
2009-07-18 18:27         ` Dave Korn

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=90baa01f0907181227x699647a3nd1a60b88888b6a7b@mail.gmail.com \
    --to=ktietz70@googlemail.com \
    --cc=aph@redhat.com \
    --cc=dave.korn.cygwin@googlemail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=java@gcc.gnu.org \
    --cc=pinskia@gmail.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).