public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libfortran/83282] missing comma in format changes output
       [not found] <bug-83282-4@http.gcc.gnu.org/bugzilla/>
@ 2023-10-12 21:42 ` anlauf at gcc dot gnu.org
  2023-10-13 20:24 ` jvdelisle at gcc dot gnu.org
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 5+ messages in thread
From: anlauf at gcc dot gnu.org @ 2023-10-12 21:42 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83282

anlauf at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|2017-12-05 00:00:00         |2023-10-12
                 CC|                            |anlauf at gcc dot gnu.org
          Component|fortran                     |libfortran
           Keywords|                            |wrong-code

--- Comment #3 from anlauf at gcc dot gnu.org ---
I looked at parse_format_list and got lost in the forest...

@Jerry: it's a missing comma *after* the A descriptor triggering the error.

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

* [Bug libfortran/83282] missing comma in format changes output
       [not found] <bug-83282-4@http.gcc.gnu.org/bugzilla/>
  2023-10-12 21:42 ` [Bug libfortran/83282] missing comma in format changes output anlauf at gcc dot gnu.org
@ 2023-10-13 20:24 ` jvdelisle at gcc dot gnu.org
  2023-10-13 20:25 ` jvdelisle at gcc dot gnu.org
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 5+ messages in thread
From: jvdelisle at gcc dot gnu.org @ 2023-10-13 20:24 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83282

Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|unassigned at gcc dot gnu.org      |jvdelisle at gcc dot gnu.org
                 CC|                            |jvdelisle at gcc dot gnu.org

--- Comment #4 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
Assigning to myself

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

* [Bug libfortran/83282] missing comma in format changes output
       [not found] <bug-83282-4@http.gcc.gnu.org/bugzilla/>
  2023-10-12 21:42 ` [Bug libfortran/83282] missing comma in format changes output anlauf at gcc dot gnu.org
  2023-10-13 20:24 ` jvdelisle at gcc dot gnu.org
@ 2023-10-13 20:25 ` jvdelisle at gcc dot gnu.org
  2024-02-17 18:40 ` jvdelisle at gcc dot gnu.org
  2024-02-17 18:43 ` jvdelisle at gcc dot gnu.org
  4 siblings, 0 replies; 5+ messages in thread
From: jvdelisle at gcc dot gnu.org @ 2023-10-13 20:25 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83282

Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

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

* [Bug libfortran/83282] missing comma in format changes output
       [not found] <bug-83282-4@http.gcc.gnu.org/bugzilla/>
                   ` (2 preceding siblings ...)
  2023-10-13 20:25 ` jvdelisle at gcc dot gnu.org
@ 2024-02-17 18:40 ` jvdelisle at gcc dot gnu.org
  2024-02-17 18:43 ` jvdelisle at gcc dot gnu.org
  4 siblings, 0 replies; 5+ messages in thread
From: jvdelisle at gcc dot gnu.org @ 2024-02-17 18:40 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83282

--- Comment #5 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
With -std=f95 we get:

$ gfc -std=f95 pr83282.f90 
pr83282.f90:1:13:

    1 |    write(*,'(aa)') "ab", "bc"
      |             1
Error: GNU Extension: Missing comma at (1)
pr83282.f90:2:17:

    2 |    write(*,'(a"bc")') "ab"
      |                 1
Error: GNU Extension: Missing comma at (1)
pr83282.f90:3:17:

    3 |    write(*,'(a"cd"a)') "ab", "bc"
      |                 1
Error: GNU Extension: Missing comma at (1)

and -pedantic gives:

$ gfc -pedantic  pr83282.f90 
pr83282.f90:1:13:

    1 |    write(*,'(aa)') "ab", "bc"
      |             1
Warning: GNU Extension: Missing comma at (1)
pr83282.f90:2:17:

    2 |    write(*,'(a"bc")') "ab"
      |                 1
Warning: GNU Extension: Missing comma at (1)
pr83282.f90:3:17:

    3 |    write(*,'(a"cd"a)') "ab", "bc"
      |                 1
Warning: GNU Extension: Missing comma at (1)

I wonder if we should reject the missing comma outright and only allow it for
-std=legacy?

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

* [Bug libfortran/83282] missing comma in format changes output
       [not found] <bug-83282-4@http.gcc.gnu.org/bugzilla/>
                   ` (3 preceding siblings ...)
  2024-02-17 18:40 ` jvdelisle at gcc dot gnu.org
@ 2024-02-17 18:43 ` jvdelisle at gcc dot gnu.org
  4 siblings, 0 replies; 5+ messages in thread
From: jvdelisle at gcc dot gnu.org @ 2024-02-17 18:43 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83282

--- Comment #6 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
$ gfc -Wall -Werror -pedantic pr83282.f90 
pr83282.f90:1:4:

    1 |    write(*,'(aa)') "ab", "bc"
      |    1
Error: Unclassifiable statement at (1)

This is not very useful either. :o

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

end of thread, other threads:[~2024-02-17 18:43 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <bug-83282-4@http.gcc.gnu.org/bugzilla/>
2023-10-12 21:42 ` [Bug libfortran/83282] missing comma in format changes output anlauf at gcc dot gnu.org
2023-10-13 20:24 ` jvdelisle at gcc dot gnu.org
2023-10-13 20:25 ` jvdelisle at gcc dot gnu.org
2024-02-17 18:40 ` jvdelisle at gcc dot gnu.org
2024-02-17 18:43 ` jvdelisle at gcc dot gnu.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).