public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/32545]  New: Give an (compile time) error not a warning for wrong edit format statements
@ 2007-06-29 10:05 burnus at gcc dot gnu dot org
  2007-06-29 16:00 ` [Bug fortran/32545] " burnus at gcc dot gnu dot org
                   ` (6 more replies)
  0 siblings, 7 replies; 8+ messages in thread
From: burnus at gcc dot gnu dot org @ 2007-06-29 10:05 UTC (permalink / raw)
  To: gcc-bugs

Example:

read '(i0)', i
             1
Warning: Positive width required in format string at (1)

[2007-06-24 23:19:31] <jerryd> I would use gfc_notify_std instead of gfc_error
at line 849 of io.c

Turning gfc_warning into gfc_error did not work as it should. We need to do
some investagation why it does not and then trun it into gfc_notify_std.


-- 
           Summary: Give an (compile time) error not a warning for wrong
                    edit format statements
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: burnus at gcc dot gnu dot org


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


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

end of thread, other threads:[~2007-07-04  1:16 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-06-29 10:05 [Bug fortran/32545] New: Give an (compile time) error not a warning for wrong edit format statements burnus at gcc dot gnu dot org
2007-06-29 16:00 ` [Bug fortran/32545] " burnus at gcc dot gnu dot org
2007-06-29 20:06 ` jvdelisle at gcc dot gnu dot org
2007-06-29 23:23 ` jvdelisle at gcc dot gnu dot org
2007-07-04  0:40 ` patchapp at dberlin dot org
2007-07-04  1:09 ` jvdelisle at gcc dot gnu dot org
2007-07-04  1:14 ` jvdelisle at gcc dot gnu dot org
2007-07-04  1:16 ` jvdelisle 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).