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

2024-12-06 Thread jvdelisle at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109105 --- Comment #10 from Jerry DeLisle --- I found the back-port ready to go in my branch. Decided to push it.

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

2024-12-06 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109105 --- Comment #9 from GCC Commits --- The releases/gcc-14 branch has been updated by Jerry DeLisle : https://gcc.gnu.org/g:be532c74fd5e0e8bd15f0829cbb7ee079b0df910 commit r14-11068-gbe532c74fd5e0e8bd15f0829cbb7ee079b0df910 Author: Jerry DeLisle

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

2024-12-05 Thread 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|NEW |RESOLVED Resolution|---

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

2024-08-06 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109105 --- Comment #7 from GCC Commits --- The master branch has been updated by Jerry DeLisle : https://gcc.gnu.org/g:45fdf838a21e151c2c676c4fcd056032e59f commit r15-2772-g45fdf838a21e151c2c676c4fcd056032e59f Author: Jerry DeLisle Date: T

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

2024-08-06 Thread roland.illig at gmx dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109105 --- Comment #6 from Roland Illig --- (In reply to Jerry DeLisle from comment #5) > Roland, please let me know if this resolves the isseue. Regression tested on > linux-x86_64. No new test cases. Yes, from a translator's perspective, this patch

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

2024-08-06 Thread jvdelisle at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109105 --- Comment #5 from Jerry DeLisle --- Created attachment 58853 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58853&action=edit Proposed patch to clean this up. Attached patch uses a simple helper macro, CHECK_INTERFACES, to avoid the use

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

2024-03-05 Thread 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 gc

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

2023-10-16 Thread 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 na

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

2023-10-13 Thread 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

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

2023-03-17 Thread 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 --- Commen