* [Bug go/63812] Compilation error due to a large floating point constant truncated to integer
[not found] <bug-63812-4@http.gcc.gnu.org/bugzilla/>
@ 2014-11-11 4:28 ` pinskia at gcc dot gnu.org
2014-11-11 10:31 ` e29253 at jp dot ibm.com
` (2 subsequent siblings)
3 siblings, 0 replies; 4+ messages in thread
From: pinskia at gcc dot gnu.org @ 2014-11-11 4:28 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63812
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This might be an issue in mpfr and not GCC if I read GCC's code correctly.
Depending on how 2.22 is read in as a floating point value.
^ permalink raw reply [flat|nested] 4+ messages in thread* [Bug go/63812] Compilation error due to a large floating point constant truncated to integer
[not found] <bug-63812-4@http.gcc.gnu.org/bugzilla/>
2014-11-11 4:28 ` [Bug go/63812] Compilation error due to a large floating point constant truncated to integer pinskia at gcc dot gnu.org
@ 2014-11-11 10:31 ` e29253 at jp dot ibm.com
2014-11-14 5:22 ` e29253 at jp dot ibm.com
2014-11-19 10:17 ` e29253 at jp dot ibm.com
3 siblings, 0 replies; 4+ messages in thread
From: e29253 at jp dot ibm.com @ 2014-11-11 10:31 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63812
--- Comment #2 from Tatsushi Inagaki <e29253 at jp dot ibm.com> ---
(In reply to Andrew Pinski from comment #1)
> This might be an issue in mpfr and not GCC if I read GCC's code correctly.
> Depending on how 2.22 is read in as a floating point value.
Andrew,
Thank you very much for your helpful comments. Our MPFR library is 3.1.2. I
applied the cumulative patch on http://www.mpfr.org/mpfr-current/allpatches,
but it did not solve the original problem, unfortunately. How can we identify
this is an inherent limitation or a potential bug of MPFR? Any suggestions
greatly help us.
^ permalink raw reply [flat|nested] 4+ messages in thread* [Bug go/63812] Compilation error due to a large floating point constant truncated to integer
[not found] <bug-63812-4@http.gcc.gnu.org/bugzilla/>
2014-11-11 4:28 ` [Bug go/63812] Compilation error due to a large floating point constant truncated to integer pinskia at gcc dot gnu.org
2014-11-11 10:31 ` e29253 at jp dot ibm.com
@ 2014-11-14 5:22 ` e29253 at jp dot ibm.com
2014-11-19 10:17 ` e29253 at jp dot ibm.com
3 siblings, 0 replies; 4+ messages in thread
From: e29253 at jp dot ibm.com @ 2014-11-14 5:22 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63812
--- Comment #4 from Tatsushi Inagaki <e29253 at jp dot ibm.com> ---
Ian,
Thank you very much for your helpful clarification. I confirmed that the unit
test passes with both of GC and GCCGO, when we modify the test from:
assertEquals(t, "2.22 PB", HumanSize(2.22*PB))
to:
assertEquals(t, "2.22 PB", HumanSize(int64(float64(2.22*PB))))
I will propose this fix to Docker.
^ permalink raw reply [flat|nested] 4+ messages in thread* [Bug go/63812] Compilation error due to a large floating point constant truncated to integer
[not found] <bug-63812-4@http.gcc.gnu.org/bugzilla/>
` (2 preceding siblings ...)
2014-11-14 5:22 ` e29253 at jp dot ibm.com
@ 2014-11-19 10:17 ` e29253 at jp dot ibm.com
3 siblings, 0 replies; 4+ messages in thread
From: e29253 at jp dot ibm.com @ 2014-11-19 10:17 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63812
--- Comment #5 from Tatsushi Inagaki <e29253 at jp dot ibm.com> ---
Submitted a pull request to Docker:
https://github.com/docker/docker/pull/9233
^ permalink raw reply [flat|nested] 4+ messages in thread