http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35862
Tobias Burnus changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35862
--- Comment #27 from Tobias Burnus ---
Author: burnus
Date: Sun Jul 21 11:54:27 2013
New Revision: 201093
URL: http://gcc.gnu.org/viewcvs?rev=201093&root=gcc&view=rev
Log:
2013-07-21 Tobias Burnus
PR fortran/35862
* libgfortra
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35862
--- Comment #26 from Uroš Bizjak ---
(In reply to Tobias Burnus from comment #24)
> [Somehow printf doesn't like my long double/__float128 example and prints
> 0.0 (long double) or garbage numbers (__float128).]
You should use %25.22Lf instead o
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35862
--- Comment #25 from Tobias Burnus ---
Rounding on input. Patch, which sets the CPU rounding mode and relies on strtof
to honour it: http://gcc.gnu.org/ml/fortran/2013-07/msg00042.html
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35862
--- Comment #24 from Tobias Burnus ---
Created attachment 30458
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30458&action=edit
Proof of concept (.c file)
Proof of concept test case (in C, tested on x86-64-gnu linux with libc 2.17).
[Someh
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35862
Tobias Burnus changed:
What|Removed |Added
CC||burnus at gcc dot gnu.org
--- Comment #23
--- Comment #22 from burnus at gcc dot gnu dot org 2010-07-12 08:07 ---
Implemented: Rounding on output.
TODO: Rounding on input. Current result for the program below is:
0.1000149011611938E+00
0.1000149011611938E+00
0.1555E+00
0.1000
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Added
AssignedTo|jvdelisle at gcc dot gnu dot|unassigned at gcc dot gnu
|org
--- Comment #21 from jvdelisle at gcc dot gnu dot org 2009-10-10 23:02
---
Subject: Bug 35862
Author: jvdelisle
Date: Sat Oct 10 23:02:11 2009
New Revision: 152632
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=152632
Log:
2009-10-10 Jerry DeLisle
PR libgfortran/358
--- Comment #20 from jvdelisle at gcc dot gnu dot org 2009-10-10 18:57
---
Subject: Bug 35862
Author: jvdelisle
Date: Sat Oct 10 18:57:35 2009
New Revision: 152627
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=152627
Log:
2009-10-10 Jerry DeLisle
PR libgfortran/358
--- Comment #19 from jvdelisle at gcc dot gnu dot org 2009-10-10 17:55
---
Reoly to Comment #17: See PR41612. I committed a fix to round_2.f03 that
tests for the kind parameter being valid and also adds kind=8 checking.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35862
--- Comment #18 from jvdelisle at verizon dot net 2009-10-10 16:03 ---
Subject: Re: [F2003] Implement new rounding modes for
run time
On Sat, 2009-10-10 at 15:45 +, danglin at gcc dot gnu dot org wrote:
>
> --- Comment #17 from danglin at gcc dot gnu dot org 2009-10-10 15:45
--- Comment #17 from danglin at gcc dot gnu dot org 2009-10-10 15:45
---
round_2.f03 fails on hppa-unknown-linux-gnu:
Excess errors:
/home/dave/gnu/gcc-4.5/gcc/gcc/testsuite/gfortran.dg/round_2.f03:6: Error:
Missing kind-parameter at (1)
/home/dave/gnu/gcc-4.5/gcc/gcc/testsuite/gfortra
--- Comment #16 from jvdelisle at gcc dot gnu dot org 2009-10-06 03:12
---
Subject: Bug 35862
Author: jvdelisle
Date: Tue Oct 6 03:12:21 2009
New Revision: 152484
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=152484
Log:
2009-10-05 Jerry DeLisle
PR libgfortran/358
--- Comment #15 from jvdelisle at gcc dot gnu dot org 2009-10-06 03:08
---
Subject: Bug 35862
Author: jvdelisle
Date: Tue Oct 6 03:08:20 2009
New Revision: 152483
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=152483
Log:
2009-10-05 Jerry DeLisle
PR libgfortran/358
--- Comment #14 from jvdelisle at gcc dot gnu dot org 2009-10-03 16:17
---
Correction to comment #13, Shifting bytes right not left. Also, I have
completed testing using memmove instead of the explicit for loop.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35862
--- Comment #13 from jvdelisle at gcc dot gnu dot org 2009-10-03 15:10
---
There are two unrelated bugs in output rounding. The following patch fixes
both. The smaller hunks were obvious. The larger gets rid of a hack I did to
handle the special case with d=0. The rounding logic alw
--- Comment #12 from jvdelisle at gcc dot gnu dot org 2009-10-02 02:32
---
Reply to comment #10: Thanks for the input and references. The perspective of
rounding before conversion to binary representation is interesting. I will
think on that a bit.
Reply to comment #11: Thanks for t
--- Comment #11 from dominiq at lps dot ens dot fr 2009-10-01 20:18 ---
There is probably a bug with round to nearest for values below 1:
print '(RN, 4F10.3)', 0.0625, 0.1875
print '(RN, 4F10.2)', 0.125, 0.375, 1.125, 1.375
print '(RN, 4F10.1)', 0.25, 0.75, 1.25, 1.75
print '(RN, 4F10.0
--- Comment #10 from burnus at gcc dot gnu dot org 2009-10-01 07:35 ---
(In reply to comment #9)
> Rounding modes are now implemented for formatted WRITE operations. I do not
> have a clear enough idea of what the rounding modes really mean for READ
> operations. For example:
>
> "Rou
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2009-10-01 01:37
---
Rounding modes are now implemented for formatted WRITE operations. I do not
have a clear enough idea of what the rounding modes really mean for READ
operations. For example:
>From Comment #4
"Rounding is done
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2009-09-29 02:51
---
Subject: Bug 35862
Author: jvdelisle
Date: Tue Sep 29 02:50:48 2009
New Revision: 152264
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=152264
Log:
2009-09-28 Jerry DeLisle
PR libgfortran/3586
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2009-09-29 02:48
---
Subject: Bug 35862
Author: jvdelisle
Date: Tue Sep 29 02:47:54 2009
New Revision: 152263
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=152263
Log:
2009-09-28 Jerry DeLisle
PR libgfortran/3586
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2009-09-29 02:44
---
Subject: Bug 35862
Author: jvdelisle
Date: Tue Sep 29 02:44:38 2009
New Revision: 152262
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=152262
Log:
2009-09-28 Jerry DeLisle
PR fortran/35862
--- Comment #5 from fxcoudert at gcc dot gnu dot org 2008-04-15 20:59
---
(In reply to comment #4)
> Well, I would argue that this digit is the most important for rounding...
Only for list-directed output and if people use really large formats (which is
a lot of cases). Otherwise, not.
--- Comment #4 from burnus at gcc dot gnu dot org 2008-04-15 19:08 ---
> I agree with you for output: we currently do COMPATIBLE rounding
I wanted to write this when I approved the code, but I found one *printf
function and checking the POSIX standard one finds:
"f, F The double argum
--- Comment #3 from fxcoudert at gcc dot gnu dot org 2008-04-15 14:02
---
I agree with you for output: we currently do COMPATIBLE rounding and it
shouldn't be too hard to change. The only case where we might not have control
is for the last significant digit output by snprintf(), where
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2008-04-09 05:15
---
After studying the F2003 standard and our code in output_float, I believe what
gfortran does now is ROUND="compatible". We round to the nearest and when
there is a tie, we round away from zero.
I think I can man
--- Comment #1 from burnus at gcc dot gnu dot org 2008-04-08 08:49 ---
> The front-end parsing and translation are completed.
Except for the r* edit descriptors.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35862
29 matches
Mail list logo