[Bug fortran/109105] Error-prone format string building in resolve.cc

[jvdelisle at gcc dot gnu.org via Gcc-bugs]

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

Jerry DeLisle  changed:

   What|Removed |Added

 Status|WAITING |NEW
   Assignee|unassigned at gcc dot gnu.org  |jvdelisle at gcc dot 
gnu.org

--- Comment #4 from Jerry DeLisle  ---
So I don't lose it.

[Bug fortran/109105] Error-prone format string building in resolve.cc

[roland.illig at gmx dot de via Gcc-bugs]

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

--- Comment #3 from Roland Illig  ---
Nothing has changed yet.

There is no built-in validation in the translated messages that each '%%L' from
the msgid matches a '%%L' from the msgstr.

I suggest to replace the label 'bad_op' with a function named 'bad_op', so that
the format strings contain '%L' instead of the current '%%L', so that gettext
can validate the format strings in the translations.

[Bug fortran/109105] Error-prone format string building in resolve.cc

[jvdelisle at gcc dot gnu.org via Gcc-bugs]

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

Jerry DeLisle  changed:

   What|Removed |Added

 Status|UNCONFIRMED |WAITING
 Ever confirmed|0   |1
   Last reconfirmed||2023-10-13

--- Comment #2 from Jerry DeLisle  ---
Roland, where do we stand on this PR?

[Bug fortran/109105] Error-prone format string building in resolve.cc

[jvdelisle at gcc dot gnu.org via Gcc-bugs]

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

Jerry DeLisle  changed:

   What|Removed |Added

 CC||jvdelisle at gcc dot gnu.org

--- Comment #1 from Jerry DeLisle  ---
Can you give an example of what this one should look like?

  snprintf (msg, sizeof (msg),
_("Inconsistent ranks for operator at %%L and %%L"));
  goto bad_op;