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
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
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
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.
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.
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.
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.
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,
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,
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".
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99291
--- Comment #6 from Roland Illig ---
Still reproducible 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.
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552
--- Comment #4 from Roland Illig ---
>From common.opt:
> an invalid linenum macros
"an" + "macros" doesn't match
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552
--- Comment #3 from Roland Illig ---
(In reply to Iain Buclaw from comment #2)
> (In reply to Roland Illig from comment #0)
> > > -fdump-cxx-spec=Write all declarations as C++ code to
> > > .
> >
> > The '' should be '' as well.
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552
Bug ID: 104552
Summary: Mistakes in strings to be translated in GCC 12
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104316
Bug ID: 104316
Summary: Missing optimization for uninitialized local struct
variable
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104044
Bug ID: 104044
Summary: Useless empty statements (across projects)
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93748
--- Comment #3 from Roland Illig ---
(In reply to Andrew Pinski from comment #2)
> Since all 4 are internal compiler error, they will not be used for
> translation and the rules for diagnostic does not need to apply here.
Are you sure about the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95177
--- Comment #17 from Roland Illig ---
(In reply to Francois-Xavier Coudert from comment #16)
> I feel like the "array subscript has type char" error is really a red
> herring in this case.
I agree, especially for C programmers who are not aware
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103457
--- Comment #2 from Roland Illig ---
Cool, thank you for taking this optimization.
Just to give you a bit of background: I discovered this while converting some
of the enum types in BSD Make to proper bitfields, which theoretically should
be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103457
Bug ID: 103457
Summary: boolean operations on bit-fields are not merged
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95177
--- Comment #15 from Roland Illig ---
(In reply to Steve Kargl from comment #9)
> I'm still trying to understand how an
> option names -Werror=char-subscripts could trigger an
> error. There are no subscripts.
There _are_ subscripts, just look
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102998
--- Comment #1 from Roland Illig ---
> for the following redeclarations
That's wrong. There is only 1 redeclaration in the code that follows.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102998
Bug ID: 102998
Summary: Wrong documentation for -Warray-parameter
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101400
Bug ID: 101400
Summary: comments mention gnu-attributes[opt] even though it
can be empty
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
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
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
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".
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
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:
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.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83773
Roland Illig changed:
What|Removed |Added
CC||roland.illig at gmx dot de
--- Comment
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.
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
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.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99303
--- Comment #1 from Roland Illig ---
This typo appears 2 times.
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
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
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
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:
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
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.
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 %.
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'.
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.
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.
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:
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
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
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99278
--- Comment #4 from Roland Illig ---
And another one: 'expectting'
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
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'
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
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
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
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
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
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".
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.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97834
Roland Illig changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
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
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
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
101 - 165 of 165 matches
Mail list logo
