public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/24636]  New: gfortran: STOP without stop-code too noisy, regression w.r.t. g77
@ 2005-11-02 14:10 anlauf at gmx dot de
  2005-11-02 14:59 ` [Bug fortran/24636] " pinskia at gcc dot gnu dot org
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: anlauf at gmx dot de @ 2005-11-02 14:10 UTC (permalink / raw)
  To: gcc-bugs

Hi,

as it has bothered me for quite some time, I finally
decided to report.  The program

      program gfcbug29
      stop
      end

when compiled with g77, executes and terminates without any message.
*Only* when a stop code is present, as in
      stop 0
it (the g77 runtime) says so.  However, gfortran always makes it
write the message, even when no stop code is present:
STOP 0

g77 is consistent with all other compilers that I have access to,
and also the F2003 draft standard (sec. 8.4) is quite explicit here.

Please fix.

Cheers,
-ha


-- 
           Summary: gfortran: STOP without stop-code too noisy, regression
                    w.r.t. g77
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: anlauf at gmx dot de
  GCC host triplet: i686-pc-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24636


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug fortran/24636] gfortran: STOP without stop-code too noisy, regression w.r.t. g77
  2005-11-02 14:10 [Bug fortran/24636] New: gfortran: STOP without stop-code too noisy, regression w.r.t. g77 anlauf at gmx dot de
@ 2005-11-02 14:59 ` pinskia at gcc dot gnu dot org
  2005-11-02 18:28 ` kargl at gcc dot gnu dot org
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2005-11-02 14:59 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #1 from pinskia at gcc dot gnu dot org  2005-11-02 14:59 -------
Confirmed, this is more of a front-end issue than a library issue.  As the
front-end emits a call to _gfortran_stop_numeric in both the STOP cases.


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
          Component|libfortran                  |fortran
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2005-11-02 14:59:16
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24636


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug fortran/24636] gfortran: STOP without stop-code too noisy, regression w.r.t. g77
  2005-11-02 14:10 [Bug fortran/24636] New: gfortran: STOP without stop-code too noisy, regression w.r.t. g77 anlauf at gmx dot de
  2005-11-02 14:59 ` [Bug fortran/24636] " pinskia at gcc dot gnu dot org
@ 2005-11-02 18:28 ` kargl at gcc dot gnu dot org
  2005-11-04 22:18 ` kargl at gcc dot gnu dot org
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: kargl at gcc dot gnu dot org @ 2005-11-02 18:28 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #2 from kargl at gcc dot gnu dot org  2005-11-02 18:27 -------
This has bugged me also.  For a patch, see

http://gcc.gnu.org/ml/gcc-patches/2005-11/msg00122.html


-- 

kargl at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kargl at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24636


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug fortran/24636] gfortran: STOP without stop-code too noisy, regression w.r.t. g77
  2005-11-02 14:10 [Bug fortran/24636] New: gfortran: STOP without stop-code too noisy, regression w.r.t. g77 anlauf at gmx dot de
  2005-11-02 14:59 ` [Bug fortran/24636] " pinskia at gcc dot gnu dot org
  2005-11-02 18:28 ` kargl at gcc dot gnu dot org
@ 2005-11-04 22:18 ` kargl at gcc dot gnu dot org
  2005-11-04 23:21 ` kargl at gcc dot gnu dot org
  2005-11-04 23:24 ` kargl at gcc dot gnu dot org
  4 siblings, 0 replies; 6+ messages in thread
From: kargl at gcc dot gnu dot org @ 2005-11-04 22:18 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #3 from kargl at gcc dot gnu dot org  2005-11-04 22:18 -------
Subject: Bug 24636

Author: kargl
Date: Fri Nov  4 22:18:22 2005
New Revision: 106509

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=106509
Log:
        PR fortran/24636
        * match.c (gfc_match_stopcode):  Set stop_code = -1.
        * runtime/stop.c (stop_numeric): Use stop_code = -1.


Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/match.c
    trunk/libgfortran/ChangeLog
    trunk/libgfortran/runtime/stop.c


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24636


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug fortran/24636] gfortran: STOP without stop-code too noisy, regression w.r.t. g77
  2005-11-02 14:10 [Bug fortran/24636] New: gfortran: STOP without stop-code too noisy, regression w.r.t. g77 anlauf at gmx dot de
                   ` (2 preceding siblings ...)
  2005-11-04 22:18 ` kargl at gcc dot gnu dot org
@ 2005-11-04 23:21 ` kargl at gcc dot gnu dot org
  2005-11-04 23:24 ` kargl at gcc dot gnu dot org
  4 siblings, 0 replies; 6+ messages in thread
From: kargl at gcc dot gnu dot org @ 2005-11-04 23:21 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #4 from kargl at gcc dot gnu dot org  2005-11-04 23:21 -------
Subject: Bug 24636

Author: kargl
Date: Fri Nov  4 23:21:36 2005
New Revision: 106510

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=106510
Log:
        PR fortran/24636
        * match.c (gfc_match_stopcode):  Set stop_code = -1.
        * runtime/stop.c (stop_numeric): Use stop_code = -1.


Modified:
    branches/gcc-4_0-branch/gcc/fortran/ChangeLog
    branches/gcc-4_0-branch/gcc/fortran/match.c
    branches/gcc-4_0-branch/libgfortran/ChangeLog
    branches/gcc-4_0-branch/libgfortran/runtime/stop.c


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24636


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug fortran/24636] gfortran: STOP without stop-code too noisy, regression w.r.t. g77
  2005-11-02 14:10 [Bug fortran/24636] New: gfortran: STOP without stop-code too noisy, regression w.r.t. g77 anlauf at gmx dot de
                   ` (3 preceding siblings ...)
  2005-11-04 23:21 ` kargl at gcc dot gnu dot org
@ 2005-11-04 23:24 ` kargl at gcc dot gnu dot org
  4 siblings, 0 replies; 6+ messages in thread
From: kargl at gcc dot gnu dot org @ 2005-11-04 23:24 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #5 from kargl at gcc dot gnu dot org  2005-11-04 23:24 -------
Fixed.


-- 

kargl at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED
   Target Milestone|---                         |4.0.3


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24636


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2005-11-04 23:24 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-11-02 14:10 [Bug fortran/24636] New: gfortran: STOP without stop-code too noisy, regression w.r.t. g77 anlauf at gmx dot de
2005-11-02 14:59 ` [Bug fortran/24636] " pinskia at gcc dot gnu dot org
2005-11-02 18:28 ` kargl at gcc dot gnu dot org
2005-11-04 22:18 ` kargl at gcc dot gnu dot org
2005-11-04 23:21 ` kargl at gcc dot gnu dot org
2005-11-04 23:24 ` kargl at gcc dot gnu dot org

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).