From: Marc Glisse <marc.glisse@inria.fr>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Uros Bizjak <ubizjak@gmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Andrew Pinski <pinskia@gmail.com>,
Richard Biener <richard.guenther@gmail.com>,
Trevor Saunders <tsaunders@mozilla.com>
Subject: Re: [PATCH] c++ify sreal
Date: Tue, 11 Nov 2014 09:24:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.11.1411111019390.1640@laptop-mg.saclay.inria.fr> (raw)
In-Reply-To: <20141111081157.GY5026@tucnak.redhat.com>
On Tue, 11 Nov 2014, Jakub Jelinek wrote:
> On Tue, Nov 11, 2014 at 08:51:41AM +0100, Uros Bizjak wrote:
>> Hello!
>>
>>>>> do $subject, and cleanup for always 64 bit hwi.
>>>>>
>>>>>
>>>>> bootstrapped + regtested x86_64-unknown-linux-gnu, ok?
>>>>
>>>> Ok. Can you please replace remaining HOST_WIDE_INT
>>>> vestiges in there with [u]int64_t please?
>>>
>>>
>>> This patch breaks the build on debian 6.0:
>>>
>>> ../../gcc/sreal.c: In member function âint64_t sreal::to_int() constâ:
>>> ../../gcc/sreal.c:159: error: âINT64_MAXâ was not declared in this scope
>>
>> Index: system.h
>> ===================================================================
>> --- system.h (revision 217338)
>> +++ system.h (working copy)
>> @@ -27,6 +27,7 @@
>> event inttypes.h gets pulled in by another header it is already
>> defined. */
>> #define __STDC_FORMAT_MACROS
>> +#define __STDC_LIMIT_MACROS
>>
>> /* We must include stdarg.h before stdio.h. */
>> #include <stdarg.h>
>
> Still, I don't believe it will be portable everywhere.
> Can't you use
> INTTYPE_MAXIMUM (int64_t) instead of INT64_MAX? We already use that
> in GCC...
We could also start using the standard C++ mechanism (numeric_limits).
(nothing wrong with INTTYPE_MAXIMUM, just an alternative)
--
Marc Glisse
next prev parent reply other threads:[~2014-11-11 9:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 8:04 Uros Bizjak
2014-11-11 8:31 ` Jakub Jelinek
2014-11-11 8:48 ` Uros Bizjak
2014-11-11 8:55 ` Jakub Jelinek
2014-11-11 9:24 ` Marc Glisse [this message]
2014-11-11 12:11 ` Andrew Pinski
2014-11-11 12:56 ` Richard Biener
2014-11-11 12:57 ` Andrew Pinski
-- strict thread matches above, loose matches on Subject: below --
2014-10-24 6:30 tsaunders
2014-10-24 8:56 ` Richard Biener
2014-11-11 6:51 ` Andrew Pinski
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=alpine.DEB.2.11.1411111019390.1640@laptop-mg.saclay.inria.fr \
--to=marc.glisse@inria.fr \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=pinskia@gmail.com \
--cc=richard.guenther@gmail.com \
--cc=tsaunders@mozilla.com \
--cc=ubizjak@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).