[Bug fortran/43851] Add _gfortran_error_stop_numeric

2010-07-19 Thread burnus at gcc dot gnu dot org
--- Comment #10 from burnus at gcc dot gnu dot org 2010-07-19 13:47 --- (In reply to comment #9) > There is one last improvement we can do here. Currently we are using > gfc_match_init_expr. This works fine, but the error messages are worded > toward > initialization expressions and n

[Bug fortran/43851] Add _gfortran_error_stop_numeric

2010-07-19 Thread jvdelisle at gcc dot gnu dot org
--- Comment #11 from jvdelisle at gcc dot gnu dot org 2010-07-20 01:07 --- Not needed. Closing. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/43851] Add _gfortran_error_stop_numeric

2010-04-22 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2010-04-22 13:30 --- Additionally, the (ERROR) STOP output should be printed to STDERR and not to STDOUT per: "8.4 STOP and ERROR STOP statements" (F2008 FDIS): "If any exception (cf. 14 Exceptions and IEEE arithmetic) is signaling on t

[Bug fortran/43851] Add _gfortran_error_stop_numeric

2010-05-08 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2010-05-08 13:06 --- Working on it. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Assigne

[Bug fortran/43851] Add _gfortran_error_stop_numeric

2010-05-13 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2010-05-13 16:58 --- I have a revised patch that handles default integer and negative error codes. It is testing and I will submit when I get an opportunity. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43851

[Bug fortran/43851] Add _gfortran_error_stop_numeric

2010-05-19 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2010-05-20 04:44 --- Subject: Bug 43851 Author: jvdelisle Date: Thu May 20 04:44:11 2010 New Revision: 159609 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=159609 Log: 2010-05-19 Jerry DeLisle PR fortran/43851

[Bug fortran/43851] Add _gfortran_error_stop_numeric

2010-05-20 Thread burnus at gcc dot gnu dot org
--- Comment #5 from burnus at gcc dot gnu dot org 2010-05-20 07:40 --- TODO: Constraint checks are missing and partially incorrect, cf. http://gcc.gnu.org/ml/fortran/2010-05/msg00225.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43851

[Bug fortran/43851] Add _gfortran_error_stop_numeric

2010-05-20 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2010-05-20 13:33 --- Also have one tweak to do for blank STOP which I will fix shortly and add some test cases. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43851

[Bug fortran/43851] Add _gfortran_error_stop_numeric

2010-05-20 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2010-05-20 19:40 --- Subject: Bug 43851 Author: jvdelisle Date: Thu May 20 19:40:30 2010 New Revision: 159638 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=159638 Log: 2010-05-20 Jerry DeLisle PR fortran/43851

[Bug fortran/43851] Add _gfortran_error_stop_numeric

2010-05-22 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2010-05-23 00:00 --- Subject: Bug 43851 Author: jvdelisle Date: Sun May 23 00:00:17 2010 New Revision: 159747 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=159747 Log: 2010-05-22 Jerry DeLisle PR fortran/43851

[Bug fortran/43851] Add _gfortran_error_stop_numeric

2010-06-05 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2010-06-06 06:10 --- There is one last improvement we can do here. Currently we are using gfc_match_init_expr. This works fine, but the error messages are worded toward initialization expressions and not stop codes. We could genera