From: Kai Tietz <ktietz70@googlemail.com>
To: Paolo Carlini <paolo.carlini@oracle.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
"libstdc++" <libstdc++@gcc.gnu.org>
Subject: Re: [patch libstdc++]: Fix LLP64 pointer-size issues for cxxabi, eh_alloc, and hash_bytes
Date: Fri, 21 Dec 2012 09:36:00 -0000 [thread overview]
Message-ID: <CAEwic4bfxyJ9JWp1qQd0rLP8zHhTRVssMEFU1=2Pcevs3JZjMA@mail.gmail.com> (raw)
In-Reply-To: <50D42CAB.4090704@oracle.com>
2012/12/21 Paolo Carlini <paolo.carlini@oracle.com>:
> Hi,
>
>
> On 12/21/2012 10:16 AM, Kai Tietz wrote:
>>
>> Well, I thought it is always present for gcc due gstdint.h header,
>
> As far as I know, that project isn't finished yet, there are still targets
> which neither provide the header, neither GCC synthetizes it. See also
> "dg-require-effective-target stdint_types".
>
>> but well, using ptrdiff_t here instead would be ok too IMHO, and later is
>> compatible to none C99-systems. Ok, with that change (and remove of later
>> cast to ptrdiff_t for it)?
>
> Are we 100% sure that, besides the targets we know well and love, elsewhere
> long is always == ptrdiff_t?
>
> Paolo.
well, issue isn't that 'long' is always 'ptrdiff_t'. As this is
indeed the wrong assumption here. As we treat here pointers later-one
as pointer-diff, it doesn't make any difference, even if pointer-size
might exceed 'ptrdiff_t' (well size_t would have here the same issue,
and all in all we lack a longptr_t type-definition in standard), then
we still don't change behavior AFAICS.
Kai
next prev parent reply other threads:[~2012-12-21 9:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-21 8:00 Kai Tietz
2012-12-21 9:12 ` Marc Glisse
2012-12-21 9:13 ` Paolo Carlini
2012-12-21 9:16 ` Kai Tietz
2012-12-21 9:32 ` Paolo Carlini
2012-12-21 9:36 ` Kai Tietz [this message]
2012-12-21 9:39 ` Paolo Carlini
2012-12-21 9:48 ` Kai Tietz
2012-12-21 9:59 ` Kai Tietz
2012-12-21 10:02 ` Paolo Carlini
2012-12-21 15:04 ` Gabriel Dos Reis
2012-12-21 15:54 ` Kai Tietz
2012-12-21 14:59 ` Gabriel Dos Reis
2012-12-21 10:13 Uros Bizjak
2012-12-21 10:16 ` Kai Tietz
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='CAEwic4bfxyJ9JWp1qQd0rLP8zHhTRVssMEFU1=2Pcevs3JZjMA@mail.gmail.com' \
--to=ktietz70@googlemail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=paolo.carlini@oracle.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).