[Bug c/99295] [9/10 Regression] documentation on __attribute__((malloc)) is wrong

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99295 --- Comment #6 from Roland Illig --- Thank you for updating the documentation. It reads really nice now and explains everything I would need or like to know when I stumble upon this function attribute.

[Bug target/99733] New: darwin: missing ':' in error message about munmap

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99733 Bug ID: 99733 Summary: darwin: missing ':' in error message about munmap Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug target/99733] darwin: missing ':' in error message about munmap

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99733 --- Comment #3 from Roland Illig --- (In reply to Iain Sandoe from comment #2) > Personally, I would have preferred "'pch_address_space' : " but that > triggers another warning about punctuation in diagnostics. So I left the > colon out (on purpo

[Bug translation/90183] ambiguous diagnostics "only available with"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90183 --- Comment #3 from Roland Illig --- In the German translation of GCC I consistently use "available since".

[Bug c/99950] New: Option -Wchar-subscripts leads to wrong fixes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99950 Bug ID: 99950 Summary: Option -Wchar-subscripts leads to wrong fixes Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug gcov-profile/97834] New: gcov-instrumented binaries are very slow due to unbuffered IO

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97834 Bug ID: 97834 Summary: gcov-instrumented binaries are very slow due to unbuffered IO Product: gcc Version: 10.1.0 Status: UNCONFIRMED Severity: normal

[Bug gcov-profile/97834] gcov-instrumented binaries are very slow due to unbuffered IO

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97834 --- Comment #4 from Roland Illig --- (In reply to Nathan Sidwell from comment #3) > gcov has its own buffer. I wish the above were true. Using gcov from GCC 5.5.0, ktrace shows that the actual buffer size is 0. That's consistent with the setbu

[Bug gcov-profile/97834] gcov-instrumented binaries are very slow due to unbuffered IO

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97834 --- Comment #7 from Roland Illig --- (In reply to Nathan Sidwell from comment #5) > you're looking in the wrong place. see gcov_var and GCOV_BLOCK_SIZE. Hmmm, this looks like there is some buffering. But still, in gcov_open, when I comment out

[Bug gcov-profile/97834] gcov-instrumented binaries are very slow due to unbuffered IO

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

[Bug gcov-profile/97834] gcov-instrumented binaries are very slow due to unbuffered IO

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97834 --- Comment #9 from Roland Illig --- (In reply to Roland Illig from comment #7) > I wonder why on NetBSD there is no buffering but on Linux there is. > Both stdio implementations are so old that I don't expect any bugs > in this area anymore. It

[Bug translation/93759] Invalid % in param

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93759 --- Comment #7 from Roland Illig --- Is there still something to do for this bug? de.po looks good now, having "c-no-format" instead of "c-format".

[Bug c/99075] New: Wrong classification of functions memchr and memcpy

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99075 Bug ID: 99075 Summary: Wrong classification of functions memchr and memcpy Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component

[Bug translation/99167] New: typo in params.opt: accesse

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99167 Bug ID: 99167 Summary: typo in params.opt: accesse Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: translation

[Bug c/99275] New: missing space in 'argument missing terminating nul'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99275 Bug ID: 99275 Summary: missing space in 'argument missing terminating nul' Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component

[Bug c/99276] New: grammar in diagnostics for overflowing the destination

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99276 Bug ID: 99276 Summary: grammar in diagnostics for overflowing the destination Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Compon

[Bug c/99278] New: typo in diagnostic: 'may reade'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99278 Bug ID: 99278 Summary: typo in diagnostic: 'may reade' Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assign

[Bug c/99278] typo in diagnostic: 'may reade'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99278 --- Comment #2 from Roland Illig --- Another trivial typo, also in builtins.c: 'epecting' should be 'expecting'

[Bug c/99280] New: argument to warning_n must be a string literal

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99280 Bug ID: 99280 Summary: argument to warning_n must be a string literal Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug c/99278] typo in diagnostic: 'may reade'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99278 --- Comment #4 from Roland Illig --- And another one: 'expectting'

[Bug c/99288] New: xgettext does not get HOST_WIDE_INT_PRINT_UNSIGNED

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99288 Bug ID: 99288 Summary: xgettext does not get HOST_WIDE_INT_PRINT_UNSIGNED Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug c/99288] xgettext does not get HOST_WIDE_INT_PRINT_UNSIGNED

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99288 --- Comment #1 from Roland Illig --- same in ipa-devirt.c: > inform (this_enum.vals[j].locus, > "name %qs is defined to " HOST_WIDE_INT_PRINT_DEC

[Bug c/99291] New: maybe_warn_pass_by_reference uses outdated format string

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99291 Bug ID: 99291 Summary: maybe_warn_pass_by_reference uses outdated format string Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priori

[Bug c/99295] New: documentation on __attribute__((malloc)) is wrong

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99295 Bug ID: 99295 Summary: documentation on __attribute__((malloc)) is wrong Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug c/99295] documentation on __attribute__((malloc)) is wrong

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99295 --- Comment #1 from Roland Illig --- The sentence s3 refers to "this property" as well, and for calloc, the documentation had been wrong for GCC 4 already since that function returns zero-initalized memory, not uninitialized memory.

[Bug c/99291] maybe_warn_pass_by_reference uses outdated format string

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99291 --- Comment #1 from Roland Illig --- similarly in common/config/riscv/riscv-common.c: > %<-march=%s%>: Extension `%s' appear more than one time. The `%s' is obsolete and should be replaced with %qs.

[Bug c/99291] maybe_warn_pass_by_reference uses outdated format string

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99291 --- Comment #2 from Roland Illig --- Plus, there is a typo: > %<-march=%s%>: Extension `%s' appear more than one time. Either it must be 'Extensions' or 'appears'.

[Bug c/99291] maybe_warn_pass_by_reference uses outdated format string

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99291 --- Comment #3 from Roland Illig --- same file, another one: > "version of `g` will be omitted, please " This is far from any coding conventions and should rather be %.

[Bug c/99291] maybe_warn_pass_by_reference uses outdated format string

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99291 --- Comment #4 from Roland Illig --- and another one, this time in aarch64.c: > error ("%<%s%> must be by itself for %<-mharden-sls=%>", str); This should be %qs as well.

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99297 Bug ID: 99297 Summary: wrong diagnostic style in rx.c Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assigne

[Bug c++/99298] New: diagnostic in name-lookup.c embeds part-of-speech

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99298 Bug ID: 99298 Summary: diagnostic in name-lookup.c embeds part-of-speech Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug fortran/99300] New: double space in diagnostic

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99300 Bug ID: 99300 Summary: double space in diagnostic Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assig

[Bug fortran/99302] New: untranslated diagnostic from gfc_compare_interfaces

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99302 Bug ID: 99302 Summary: untranslated diagnostic from gfc_compare_interfaces Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component

[Bug fortran/99303] New: OpenMP: typo in diagnostic

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99303 Bug ID: 99303 Summary: OpenMP: typo in diagnostic Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assig

[Bug fortran/99303] OpenMP: typo in diagnostic

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99303 --- Comment #1 from Roland Illig --- This typo appears 2 times.

[Bug fortran/99303] OpenMP: typo in diagnostic

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99303 --- Comment #2 from Roland Illig --- same file, other typo: > "clauses on the same construct %L" The "at %L" is missing.

[Bug c/99304] New: typo in diagnostic: refernced

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99304 Bug ID: 99304 Summary: typo in diagnostic: refernced Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee

[Bug c/99304] [11 Regression] typo in diagnostic: refernced

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99304 --- Comment #4 from Roland Illig --- Thank you for fixing the typos. Could you perhaps add the test cases to the test suite, to have the two diagnostics covered? Now that the typo is fixed, both should trivially pass.

[Bug preprocessor/83773] Create new switch, -Wmacro-redefined, to control warning for redefined macro

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83773 Roland Illig changed: What|Removed |Added CC||roland.illig at gmx dot de --- Comment #4

[Bug target/101177] New: sh3: internal compiler error: Illegal instruction

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101177 Bug ID: 101177 Summary: sh3: internal compiler error: Illegal instruction Product: gcc Version: 9.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Componen

[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 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 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] 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 #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 #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 #5 from Roland Illig --- While here: > dependancies Typo; should be dependencies.

[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 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 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 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 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 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 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 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 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 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 translation/104552] Mistakes in strings to be translated in GCC 12

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552 --- Comment #7 from Roland Illig --- >From params.opt: > When propagating IPA-CP effect estimates, multiply frequencies of recursive > edges that that bring back an unchanged value by this factor. "that that" >From params.opt: > Maximum combin

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552 --- Comment #8 from Roland Illig --- >From tree-ssa-uninit.c: > accessing argument %u of a function declared with attribute %<%s%> The %<%s%> should be the conventional %qs.

[Bug c/99291] maybe_warn_pass_by_reference uses outdated format string

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99291 --- Comment #6 from Roland Illig --- Still reproducible in GCC 12.

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552 --- Comment #9 from Roland Illig --- >From config/host-darwin.cc: > error ("PCH memory not available %m"); Looks like a missing ":" before "%m".

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552 --- Comment #10 from Roland Illig --- >From aarch64-sve-builtins.cc: > error_at (location, "passing single vector %qT to argument %d" > " of %qE, which expects a tuple of %d vectors", > actual, argno + 1, fndecl, num_vectors)

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552 --- Comment #11 from Roland Illig --- >From aarch64-sve-builtins.cc: > passing %qT to argument %d of %qE, which expects a scalar integer "scalar integer" sounds redundant, this may be a copy-and-paste mistake from the message directly above, wh

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552 --- Comment #12 from Roland Illig --- >From aarch64-sve-builtins.cc: > "capture by copy of SVE type %qT" This message should use the same grammar as the related ones, the word "cannot" is a useful indicator of the general error condition.

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552 --- Comment #13 from Roland Illig --- >From aarch64.cc: > invalid feature modifier %s The %s must be %qs, like in the related messages.

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552 --- Comment #14 from Roland Illig --- >From aarch64.cc: > "invalid name (%qs) in % pragma or attribute" What is the point of having parentheses around %qs? That seems redundant to me.

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552 --- Comment #15 from Roland Illig --- >From aarch64.cc: > arch extension %<%s%> Use the idiomatic %qs instead.

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552 --- Comment #16 from Roland Illig --- >From arm-builtins.cc: > "the range of count should be in 0 to 32; > please check the intrinsic %<_mm_rori_pi16%> in code" Please double-check whether the "0 to 32" is a typo and should rather be "0 to 16".

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104794 Bug ID: 104794 Summary: arm: use translation pattern for repetitive messages Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Compon

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104794 --- Comment #1 from Roland Illig --- >From arm-builtins.cc: > "the range of count should be in 0 to 32; > please check the intrinsic %<_mm_rori_pi16%> in code" While here, please double-check whether the "0 to 32" is a typo and should rather be

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104794 --- Comment #2 from Roland Illig --- While here, please add the missing space in the middle of the string: error ("incompatible options %'-mstack-protector-guard=global%' and" "%'-mstack-protector-guard-offset=%qs%'",

[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 %'...%'.

[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 #5 from Roland Illig --- Same for %'-mstack-protector-guard=tls%' in the same file.

[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/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 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/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 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 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 #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/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 #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 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/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 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/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 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 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++/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 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 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 #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 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 #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++/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 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 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 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 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] 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?

  1   2   >