From: Uros Bizjak <ubizjak@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: "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 08:48:00 -0000 [thread overview]
Message-ID: <CAFULd4ZM8FaqBGJkDSc5+R_mdai0SuDoUfEby5=8hDZgw9wUDw@mail.gmail.com> (raw)
In-Reply-To: <20141111081157.GY5026@tucnak.redhat.com>
On Tue, Nov 11, 2014 at 9:11 AM, Jakub Jelinek <jakub@redhat.com> wrote:
>> >>> 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
>>
> 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...
Yes, following patch also bootstraps:
--cut here--
Index: sreal.c
===================================================================
--- sreal.c (revision 217338)
+++ sreal.c (working copy)
@@ -156,7 +156,7 @@ sreal::to_int () const
if (m_exp <= -SREAL_BITS)
return 0;
if (m_exp >= SREAL_PART_BITS)
- return INT64_MAX;
+ return INTTYPE_MAXIMUM (int64_t);
if (m_exp > 0)
return m_sig << m_exp;
if (m_exp < 0)
--cut here--
Uros.
next prev parent reply other threads:[~2014-11-11 8:45 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 [this message]
2014-11-11 8:55 ` Jakub Jelinek
2014-11-11 9:24 ` Marc Glisse
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='CAFULd4ZM8FaqBGJkDSc5+R_mdai0SuDoUfEby5=8hDZgw9wUDw@mail.gmail.com' \
--to=ubizjak@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=pinskia@gmail.com \
--cc=richard.guenther@gmail.com \
--cc=tsaunders@mozilla.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).