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

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 rust/114629] New: rust-ast-resolve-expr contains bloated code for funny_error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114629 Bug ID: 114629 Summary: rust-ast-resolve-expr contains bloated code for funny_error Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal P

[Bug translation/40883] [meta-bug] Translation breakage with trivial fixes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40883 --- Comment #13 from Roland Illig --- See also bug 114407.

[Bug target/114407] New: Typo 'enabing' in loongarch-opts.cc

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114407 Bug ID: 114407 Summary: Typo 'enabing' in loongarch-opts.cc Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: translation Severity: normal Priority: P3

[Bug fortran/80012] FIXME in diagnostic "%s procedure at %L is already declared as %s procedure" from symbol.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80012 --- Comment #8 from Roland Illig --- (In reply to Jakub Jelinek from comment #7) > (In reply to Jerry DeLisle from comment #5) > > Another way is to build an error message with snprintf for example and use > > that string in the error message. >

[Bug c/114364] Untranslatable string 'in intervening code'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114364 --- Comment #3 from Roland Illig --- The diff looks good to me. Untested.

[Bug c/114364] Untranslatable string 'in intervening code'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114364 --- Comment #1 from Roland Illig --- Oops, I misinterpreted the code, as 'in intervening code' is indeed translatable, but 'as loop variable' isn't, so the bug report is still valid.

[Bug c/114364] New: Untranslatable string 'in intervening code'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114364 Bug ID: 114364 Summary: Untranslatable string 'in intervening code' Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priori

[Bug target/114083] Possible word play on conditional/unconditional

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114083 --- Comment #6 from Roland Illig --- (In reply to Maciej W. Rozycki from comment #4) > The flag enables the use of the conditional-move operations even with > hardware that has no support for such operations, hence unconditionally. Thank you fo

[Bug target/114083] Possible word play on conditional/unconditional

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114083 --- Comment #2 from Roland Illig --- I don't understand why the word 'unconditionally' is necessary or useful here. Isn't the option -mmovcc by itself already a condition? That would make the word 'unconditionally' wrong.

[Bug driver/114082] Guidelines for options are empty

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114082 --- Comment #1 from Roland Illig --- If you decide to keep the guidelines, here are a few ideas: * Use the simplest English you can, while still being precise. * Don't try to be funny. (See #114083 for a possible case)

[Bug target/114083] New: Possible word play on conditional/unconditional

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114083 Bug ID: 114083 Summary: Possible word play on conditional/unconditional Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: documentation Severity: normal

[Bug preprocessor/114082] New: Guidelines for options are empty

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114082 Bug ID: 114082 Summary: Guidelines for options are empty Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: documentation Severity: normal Priority: P3

[Bug target/113324] internal compiler error: in reload_combine_note_use, at postreload.c:1534

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113324 Roland Illig changed: What|Removed |Added Resolution|--- |FIXED Status|WAITING

[Bug target/113324] New: internal compiler error: in reload_combine_note_use, at postreload.c:1534

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113324 Bug ID: 113324 Summary: internal compiler error: in reload_combine_note_use, at postreload.c:1534 Product: gcc Version: 10.5.0 Status: UNCONFIRMED Severity: no

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

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 target/110772] strange code generated for bit-field access

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110772 --- Comment #8 from Roland Illig --- When I compile the attached code with "ARM GCC 10.5.0" and "-O2 -fPIE -ftrapv" on godbolt.org, the generated code is correct (you can search for "#327" in the output and then go back one branch). The code ge

[Bug target/110772] strange code generated for bit-field access

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110772 --- Comment #7 from Roland Illig --- Created attachment 55612 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55612&action=edit Preprocessed source from comment 5

[Bug target/110772] strange code generated for bit-field access

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110772 Roland Illig changed: What|Removed |Added Attachment #55598|0 |1 is obsolete|

[Bug target/110772] strange code generated for bit-field access

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110772 --- Comment #5 from Roland Illig --- Sorry for the confusing description. Let me try again. NetBSD lint includes a yacc parser for C code. This parser contains the rules 'block_item_list' and 'block_item': https://github.com/NetBSD/src/blob/7e

[Bug c/110772] strange code generated for bit-field access

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110772 --- Comment #1 from Roland Illig --- Created attachment 55599 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55599&action=edit precompiled code that works as intended

[Bug c/110772] New: strange code generated for bit-field access

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110772 Bug ID: 110772 Summary: strange code generated for bit-field access Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug tree-optimization/110519] New: Optimize loop that only assigns to a local variable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110519 Bug ID: 110519 Summary: Optimize loop that only assigns to a local variable Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: normal

[Bug c/110322] New: Be more helpful when a varargs function is called in a wrong way

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110322 Bug ID: 110322 Summary: Be more helpful when a varargs function is called in a wrong way Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: diagnostic

[Bug c/110318] Unused string literal is retained in assembler file

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110318 --- Comment #1 from Roland Illig --- A variant on the same theme: ~~~c typedef typeof(sizeof 0) size_t; int memcmp(const void *, const void *, size_t); int demo(const char *s) { if (memcmp(s, "12345678", 8) == 0) return

[Bug c/110318] New: Unused string literal is retained in assembler file

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110318 Bug ID: 110318 Summary: Unused string literal is retained in assembler file Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Compone

[Bug c/110259] New: Wrong warning 'conversion to unsigned int' with enum and comma

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110259 Bug ID: 110259 Summary: Wrong warning 'conversion to unsigned int' with enum and comma Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal

[Bug c/109905] New: Missed misleading indentation with braces

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109905 Bug ID: 109905 Summary: Missed misleading indentation with braces Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug modula2/109488] New: typo in lang.opt: libraries maybe

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109488 Bug ID: 109488 Summary: typo in lang.opt: libraries maybe Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3

[Bug modula2/109315] New: typo: inconsistant

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109315 Bug ID: 109315 Summary: typo: inconsistant Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3 Component

[Bug fortran/109314] New: Typo 'composit' in diagnostic

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109314 Bug ID: 109314 Summary: Typo 'composit' in diagnostic Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3

[Bug c++/109309] New: Untranslated text in diagnostic

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109309 Bug ID: 109309 Summary: Untranslated text in diagnostic Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3

[Bug gcov-profile/109297] New: typo: subcomand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109297 Bug ID: 109297 Summary: typo: subcomand Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: gcov-profile Assignee:

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109105 Bug ID: 109105 Summary: Error-prone format string building in resolve.cc Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: translation Severity: normal

[Bug other/109103] New: Missing function internal_error_at

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109103 Bug ID: 109103 Summary: Missing function internal_error_at Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other

[Bug modula2/109102] New: Wrong quotes in diagnostic

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109102 Bug ID: 109102 Summary: Wrong quotes in diagnostic Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: modula2 Ass

[Bug fortran/109101] New: Wrong quotes in OpenMP diagnostic

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109101 Bug ID: 109101 Summary: Wrong quotes in OpenMP diagnostic Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran

[Bug target/109100] Possible typo CRS

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109100 --- Comment #1 from Roland Illig --- While here: In that same message, there is a single space between sentences 1 and 2, but 2 spaces between sentences 2 and 3. While here: can not is usually spelled cannot.

[Bug target/109100] New: Possible typo CRS

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109100 Bug ID: 109100 Summary: Possible typo CRS Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: una

[Bug c/109034] Missing space in diagnostics about '^' and '<<'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109034 --- Comment #1 from Roland Illig --- While here: > "you can silence this warning by using a hexadecimal constant" > " (%wx rather than %wd)", %x requires an unsigned argument, %wd requires a signed argument, so %wd should probably be %wu inste

[Bug c/109034] New: Missing space in diagnostics about '^' and '<<'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109034 Bug ID: 109034 Summary: Missing space in diagnostics about '^' and '<<' Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug rtl-optimization/109033] Some messages are not understandable by ordinary user

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109033 --- Comment #1 from Roland Illig --- > "%@ %s (fndecl %qD, depth %i)", Why am I supposed to translate this string? It just doesn't make sense to translate this into German, or any other natural language.

[Bug rtl-optimization/109033] New: Some messages are not understandable by ordinary user

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109033 Bug ID: 109033 Summary: Some messages are not understandable by ordinary user Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Compo

[Bug modula2/109032] message 'compiler checks to force' is too complicated

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109032 --- Comment #5 from Roland Illig --- While here: > dependancies Typo; should be dependencies.

[Bug modula2/109032] message 'compiler checks to force' is too complicated

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109032 --- Comment #4 from Roland Illig --- While here: > (* >BuildDivM2 - build and return ((op2 < 0) : (op1 divtrunc op2) ? (op1 > divfloor op2)) > when -fiso, -fpim4 or -fpositive-mod-floor-div is present else >

[Bug modula2/109032] message 'compiler checks to force' is too complicated

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109032 --- Comment #3 from Roland Illig --- While here: > specify the library order, currently legal entries include: log, min, pim, > iso or their directory name equivalent m2log, m2min, m2pim, m2iso. In what legislation are these entries "legal"?

[Bug modula2/109032] message 'compiler checks to force' is too complicated

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109032 --- Comment #2 from Roland Illig --- While here: > turns on runtime checking to check whether a floating point number is about > to exceed range What exactly does "is about to" mean, and why didn't you just write "exceeds the range"?

[Bug modula2/109032] message 'compiler checks to force' is too complicated

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109032 --- Comment #1 from Roland Illig --- While here: > turns on runtime checking to check whether a CASE statement requires an ELSE > clause when on was not specified Did you mean "when one was not"?

[Bug modula2/109032] New: message 'compiler checks to force' is too complicated

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109032 Bug ID: 109032 Summary: message 'compiler checks to force' is too complicated Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Compo

[Bug translation/108890] New: Translation mistakes 2023

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108890 Bug ID: 108890 Summary: Translation mistakes 2023 Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3 Co

[Bug tree-optimization/105295] New: missed optimization with -ftrapv for conditional constants

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105295 Bug ID: 105295 Summary: missed optimization with -ftrapv for conditional constants Product: gcc Version: 12.0 URL: https://godbolt.org/z/4rojo77a7 Status:

[Bug c/105209] New: internal compiler error: in store_data_bypass_p_1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105209 Bug ID: 105209 Summary: internal compiler error: in store_data_bypass_p_1 Product: gcc Version: 10.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Compone

[Bug translation/40883] [meta-bug] Translation breakage with trivial fixes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40883 Bug 40883 depends on bug 104552, which changed state. Bug 104552 Summary: Mistakes in strings to be translated in GCC 12 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552 What|Removed |Added --

[Bug translation/104552] Mistakes in strings to be translated in GCC 12

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552 Roland Illig changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug c++/104907] New: unclear diagnostic for fatal error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104907 Bug ID: 104907 Summary: unclear diagnostic for fatal error Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3

[Bug c++/104906] New: UTF-8 bytes output in diagnostic regardless of locale

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104906 Bug ID: 104906 Summary: UTF-8 bytes output in diagnostic regardless of locale Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal

[Bug c++/104905] New: untranslated word in diagnostic about compiled module

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104905 Bug ID: 104905 Summary: untranslated word in diagnostic about compiled module Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal

[Bug target/104904] New: misplaced quotes in diagnostic

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104904 Bug ID: 104904 Summary: misplaced quotes in diagnostic Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3

[Bug target/104903] New: missing quotes in diagnostic

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104903 Bug ID: 104903 Summary: missing quotes in diagnostic Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3

[Bug target/104902] New: missing %q in diagnostic

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104902 Bug ID: 104902 Summary: missing %q in diagnostic Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3 Com

[Bug c/104899] New: typo "cannott"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104899 Bug ID: 104899 Summary: typo "cannott" Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3 Component: c

[Bug target/104898] New: missing %q in diagnostic

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104898 Bug ID: 104898 Summary: missing %q in diagnostic Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3 Com

[Bug target/104897] New: wrong plural form in diagnostic

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104897 Bug ID: 104897 Summary: wrong plural form in diagnostic Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3

[Bug translation/104552] Mistakes in strings to be translated in GCC 12

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552 --- Comment #38 from Roland Illig --- (In reply to Roland Illig from comment #7) > From params.opt: > > --param=ranger-debug=[none|trace|gori|cache|tracegori|all] > > Specifies the output mode for debugging ranger. > > Why " " instead of the us

[Bug c/104896] New: Messages use %<%s%> instead of the idiomatic %qs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104896 Bug ID: 104896 Summary: Messages use %<%s%> instead of the idiomatic %qs Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal P

[Bug target/104794] arm: use translation pattern for repetitive messages

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104794 --- Comment #11 from Roland Illig --- Thank you, looks good now.

[Bug translation/104552] Mistakes in strings to be translated in GCC 12

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552 --- Comment #37 from Roland Illig --- I'm splitting this bug report into multiple bug reports, to clean up the mess that the 36 comments created. It was a bad idea from the beginning. :)

[Bug fortran/104888] diagnostics use non-idiomatic '%s'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104888 --- Comment #5 from Roland Illig --- Related, in trans-openmp.cc: > "specified at %L " The space at the end is too much.

[Bug fortran/104888] diagnostics use non-idiomatic '%s'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104888 --- Comment #4 from Roland Illig --- While here: > requiries typo: should be requires

[Bug fortran/104888] diagnostics use non-idiomatic '%s'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104888 --- Comment #3 from Roland Illig --- While here: > DEPEND clause of depobj Should DEPOBJ be uppercase?

[Bug fortran/104888] diagnostics use non-idiomatic '%s'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104888 --- Comment #2 from Roland Illig --- While here: > "'omp_allocator_handle_kind' kind at %L" Should this be uppercase instead?

[Bug fortran/104888] diagnostics use non-idiomatic '%s'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104888 --- Comment #1 from Roland Illig --- While here: > expected : at %C The quotes around the %<:%> are missing.

[Bug fortran/104888] New: diagnostics use non-idiomatic '%s'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104888 Bug ID: 104888 Summary: diagnostics use non-idiomatic '%s' Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3

[Bug d/104878] New: untranslated string in diagnostic "%s %qs instantiated"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104878 Bug ID: 104878 Summary: untranslated string in diagnostic "%s %qs instantiated" Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Prior

[Bug c++/104877] New: missing standard gnu++20 in diagnostic

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104877 Bug ID: 104877 Summary: missing standard gnu++20 in diagnostic Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug c++/104876] New: untranslated strings in diagnostic about failed mapper

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104876 Bug ID: 104876 Summary: untranslated strings in diagnostic about failed mapper Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal

[Bug translation/104552] Mistakes in strings to be translated in GCC 12

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552 --- Comment #35 from Roland Illig --- (In reply to rsand...@gcc.gnu.org from comment #33) > (In reply to Eric Gallager from comment #28) > > (In reply to Roland Illig from comment #11) > > > From aarch64-sve-builtins.cc: > > > > passing %qT to a

[Bug c++/104808] unclear diagnostic "MAP %qD TO %qT"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104808 --- Comment #2 from Roland Illig --- (In reply to Andrew Pinski from comment #1) > these are in debug_* functions so they don't need to be translated as they > are not user visible at all. > That is they are only used while debugging GCC. If th

[Bug translation/104552] Mistakes in strings to be translated in GCC 12

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552 --- Comment #26 from Roland Illig --- >From cp/module.cc: > returning to the gate for a mechanical issue This diagnostic is a fatal error. Fatal errors must be actionable. This diagnostic isn't actionable, instead it increases confusion for n

[Bug translation/104552] Mistakes in strings to be translated in GCC 12

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552 --- Comment #25 from Roland Illig --- >From cp/module.cc: inform (loc, "compiler is %sversion %s%s%s", IS_EXPERIMENTAL (my_ver) ? "experimental " : "", my_string, reject_p ? "" : fl

[Bug translation/104552] Mistakes in strings to be translated in GCC 12

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552 --- Comment #24 from Roland Illig --- >From cp/module.cc: > error_at (loc, "compiled module is %sversion %s", > IS_EXPERIMENTAL (their_ver) ? "experimental " : "", > their_string); The word "experimental" must be translatabl

[Bug c++/104810] New: Wrong order of "note: ... this enumerator %qD"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104810 Bug ID: 104810 Summary: Wrong order of "note: ... this enumerator %qD" Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: diagnostic, testsuite-fail Severity: norm

[Bug c++/104809] New: Explain ELRoND to translators

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104809 Bug ID: 104809 Summary: Explain ELRoND to translators Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3

[Bug c++/104808] New: unclear diagnostic "MAP %qD TO %qT"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104808 Bug ID: 104808 Summary: unclear diagnostic "MAP %qD TO %qT" Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3

[Bug translation/104552] Mistakes in strings to be translated in GCC 12

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552 --- Comment #23 from Roland Illig --- >From c-parser.cc and cp/parser.cc: > %<#pragma omp target%> with modifier other than % or %on > % clause Missing space between "%" and "on".

[Bug translation/104552] Mistakes in strings to be translated in GCC 12

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552 --- Comment #22 from Roland Illig --- >From v850-c.cc: > %<#pragma%> GHS end found without previous startXXX > %<#pragma%> GHS endXXX does not match previous startXXX > junk at end of %<#pragma%> ghs section > malformed %<#pragma%> ghs secti

[Bug translation/90148] Closing quote in wrong position in plugin.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90148 --- Comment #7 from Roland Illig --- Still reproducible in GCC 12. Any chance of these trivial things getting fixed in the next year?

[Bug target/99297] wrong diagnostic style in rx.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99297 Roland Illig changed: What|Removed |Added Version|11.0|12.0 --- Comment #1 from Roland Illig --

[Bug translation/104552] Mistakes in strings to be translated in GCC 12

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552 --- Comment #21 from Roland Illig --- >From rs6000-c.cc: > passing argument %d of %qE discards const qualifier from pointer target type The word "const" must be in % quotes.

[Bug translation/104552] Mistakes in strings to be translated in GCC 12

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552 --- Comment #20 from Roland Illig --- >From pru.cc: > register name %<%s%> Please use the canonical %qs instead of the unnecessarily verbose %<%s%>. Everywhere.

[Bug translation/104552] Mistakes in strings to be translated in GCC 12

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552 --- Comment #19 from Roland Illig --- >From nvptx.cc: > PTX version (-mptx) needs to be at least %s to support selected -misa (sm_%s) Missing %<...%> around -mptx and -misa.

[Bug translation/40883] [meta-bug] Translation breakage with trivial fixes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40883 --- Comment #11 from Roland Illig --- Is there a general plan of fixing these "trivial" nits? Half of my reports from 2019 are still open after 3 years.

[Bug translation/104552] Mistakes in strings to be translated in GCC 12

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552 --- Comment #18 from Roland Illig --- >From nds32.cc: > this built-in function not support on the v3m toolchain "support" should be "supported".

[Bug target/104797] New: too many parentheses in diagnostic for __delay_cycles

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104797 Bug ID: 104797 Summary: too many parentheses in diagnostic for __delay_cycles Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal

[Bug target/104796] New: ABI change is not mentioned in HTML changelog

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104796 Bug ID: 104796 Summary: ABI change is not mentioned in HTML changelog Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: documentation Severity: normal P

[Bug target/104795] New: inconsistent wording in diagnostics

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104795 Bug ID: 104795 Summary: inconsistent wording in diagnostics Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3

[Bug translation/104552] Mistakes in strings to be translated in GCC 12

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552 --- Comment #17 from Roland Illig --- >From bfin.cc: > cannott Should be "cannot".

[Bug target/104794] arm: use translation pattern for repetitive messages

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104794 --- Comment #5 from Roland Illig --- Same for %'-mstack-protector-guard=tls%' in the same file.

[Bug target/104794] arm: use translation pattern for repetitive messages

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104794 --- Comment #4 from Roland Illig --- And another thing: > %'-mstack-protector-guard-offset=%qs%' This produces nested quotes. The %qs should rather be a simple %s. Maybe you can write a unit test to see how the end result looks. I didn't find a

[Bug target/104794] arm: use translation pattern for repetitive messages

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104794 --- Comment #3 from Roland Illig --- While here: > error ("incompatible options %'-mstack-protector-guard=global%' and" >"%'-mstack-protector-guard-offset=%qs%'", The idiomatic way to write quotes is %<...%>, not %'...%'.

  1   2   >