https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79869
Roland Illig changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40883
Bug 40883 depends on bug 79869, which changed state.
Bug 79869 Summary: i18n: document placeholders for translators
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79869
What|Removed |Added
: translation
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From aarch64.c:
error ("missing arg for %<-mbranch-protection=%>");
The word "arg" is only allowed in code, not in diagnostics. For ex
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From arm.c:
error ("%s incompatible with %<-mword-relocations%>", flag);
The first %s is also a command line option and thus should be %qs.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90160
--- Comment #3 from Roland Illig ---
From gcn.c, one more:
error ("duplicated parameter specifier %s in amdgpu_hsa_kernel "
"attribute", str);
ty: P3
Component: translation
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
For GCC 9, all occurrences of %<%s%> had been replaced with %qs.
That must have been before 2019-01-08 since on that day the following code
appeare
: target
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From aarch64.c:
if (guard_size != probe_interval)
error ("stack clash guard size %<%d%> must be equal to probing interval "
&quo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90156
--- Comment #1 from Roland Illig ---
To fix bug 90158 thoroughly, please also add \"%s\" to the forbidden string
literals.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90158
--- Comment #1 from Roland Illig ---
The above are not the only occurrences in aarch64.c, there is at least one
more. It's easy to find: \"%s\" or a simple %s surrounded by spaces on both
ends.
See also bug 90156.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90160
--- Comment #1 from Roland Illig ---
From csky.c:
warning (0, "cpu %s is not based on arch %s, ignoring the arch",
csky_selected_cpu->name, csky_selected_arch->name);
: translation
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From aarch64.c:
error ("invalid name (\"%s\") in % pragma or attribute",
str);
Here, the "%s" should be replaced with %qs, to conform to the
Priority: P3
Component: translation
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From i386.c:
static void warn_once_call_ms2sysv_xlogues (const char *feature)
{
static bool warned_once = false;
if (!warned_once
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90148
--- Comment #2 from Roland Illig ---
From m68k.c:
error ("%<-mpcrel%> %<-fPIC%> is not currently supported on selected cpu");
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90148
--- Comment #1 from Roland Illig ---
From arm-builtins.c:
fatal_error (input_location,
"You must enable NEON instructions"
" (e.g. %<-mfloat-abi=softfp%> %<-mfpu=neon%>)"
" to use
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90160
--- Comment #2 from Roland Illig ---
From gcn.c:
error ("unknown specifier %s in amdgpu_hsa_kernel attribute", str);
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From i386.c:
warning (OPT_Wabi, "empty class %qT parameter passing ABI "
"changes in %<-fabi-version=12%> (GCC 8)", type);
Since th
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From aarch64.c:
if (opts->x_aarch64_stack_protector_guard_reg_str)
{
if (strlen (o
: translation
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From h8300.c:
warning (OPT_mno_exr, "%<-mno-exr%> valid only with %<-ms%> or "
"%<-msx%> - Option ignored!"
nt: target
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From nds32.c:
error ("Disable FPU ISA, "
"the ABI option must be enable %<-mfloat-abi=soft%>");
else
error
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90119
--- Comment #4 from Roland Illig ---
Created attachment 46207
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46207=edit
linter that checks diagnostics that only differ in placeholder content
Using polib, writing the linter was not
iority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From msp430.c:
if (is_critical_func (* node))
{
warning (OPT_Wattributes,
"critical attribute has no effe
Component: translation
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From s390.c:
error ("constant argument %d for builtin %qF is out of range "
"(0..%wu)", argnum, decl,
(HOST_WIDE_INT_1U <&
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90180
--- Comment #1 from Roland Illig ---
While here, the two diagnostics in s390_const_operand_ok are very similar. It
would be nice if the first of them had the same text as the second one, passing
the 0 as an argument.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90176
Roland Illig changed:
What|Removed |Added
Attachment #46204|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90148
--- Comment #4 from Roland Illig ---
From rx.c:
error ("use %<__builtin_rx_mvtc%> (0, ... ) to write arbitrary values to
PSW");
The closing quote should be after the closing parenthesis.
Component: translation
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From rx.c:
warning (0, "unrecognized control register number: %d"
"- using %", (int) INTVAL (op));
Between the %d and the hyphen should be a space.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90176
--- Comment #1 from Roland Illig ---
Created attachment 46204
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46204=edit
linter ported to using polib
I rewrote the linter to use polib. As this is a complete rewrite, a diff would
be less
Priority: P3
Component: translation
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From nds32.c:
if (!TREE_PUBLIC (decl))
error ("indirect_call attribute can%'t apply for static function"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90148
--- Comment #3 from Roland Illig ---
From rs6000/linux64.h:
error ("%<-mcmodel incompatible with other toc options%>"); \
The closing quote should be directly behind the "-mcmodel".
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
Since download_prerequisites is (probably) run via /bin/sh, it should use
portable shell programming constructs:
--- contrib/download_prerequisites.orig 2017-04-11 16:34
: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
The guideline for diagnostics
(https://gcc.gnu.org/onlinedocs/gccint/Guidelines-for-Diagnostics.html) says
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90149
--- Comment #1 from Roland Illig ---
Just another remark:
The words "BIT_FIELD_REF of non-mode-precision operand" do not occur anywhere
in the test suite. They should. Or did I miss something?
If this is meant to be unreachable code, it should
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90141
--- Comment #1 from Roland Illig ---
While here, the "%> %<" was probably a mistake by a recent mass update to
surround command line options with quotes. That program didn't take into
account that the two options %<-gdwarf -g%s%> form a group
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From
https://github.com/NetBSD/pkgsrc/blob/342fd468170ed3d1902196089f8b920e333b750e/lang/gcc8/patches/patch-isl_configure:
$NetBSD: patch-isl_configure,v 1.1 2018/05/05 04:08:36 maya
: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
https://github.com/NetBSD/pkgsrc/blob/342fd468170ed3d1902196089f8b920e333b750e/lang/gcc8/patches/patch-libffi_configure
$NetBSD: patch-libffi_configure,v 1.1 2018/05/05 04:08:36 maya Exp
: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From
https://github.com/NetBSD/pkgsrc/blob/342fd468170ed3d1902196089f8b920e333b750e/lang/gcc8/patches/patch-libgcc_crtstuff.c:
$NetBSD: patch-libgcc_crtstuff.c,v 1.1 2018/05/05 04:08:36 maya Exp
: translation
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From plugin.c, at the bottom:
fatal_error (input_location,
"%<-iplugindir%> option not passed from the gcc
driver");
The %&
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90164
--- Comment #2 from Roland Illig ---
(In reply to Martin Sebor from comment #1)
> Confirmed. There seems to be little consistency between "changes" and "has
> changed" -- it's 11 vs 6.
To me it looks completely consistent.
If something
mponent: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From cp/parser.c:
pedwarn (input_location, 0,
"attribute using prefix only available "
"with %<-std=c++17%> or %<-std=gnu++1
Component: translation
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
For example:
pedwarn (cp_lexer_peek_token (parser->lexer)->location,
OPT_Wpedantic, "nested inline namespace definitions only &quo
: translation
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
Fixing this issue for good is being done in bug 79618. That is more complicated
than "trivial".
In this bug I collect the trivial occurrences that shoul
ty: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From cp/parser.c:
/* http://cplusplus.github.io/EWG/ewg-active.html#66 */
pedwarn (DECL_SOURCE_LOCATION (decl), OPT
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90184
--- Comment #2 from Roland Illig ---
(In reply to Jonathan Wakely from comment #1)
> But is it confusing in context when the diagnostic points to a piece of code
> saying [[using gnu: noinline]] ?
Yes, it is. I just had a look at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90183
--- Comment #2 from Roland Illig ---
The same diagnostic also appears for %<-std=c++-17%> and several others, and
these are in the past. Are the options from these standard only available in
that particular version of the standard? I don't guess
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90163
--- Comment #3 from Roland Illig ---
(In reply to Daniel Santos from comment #2)
> Yes, this is mine. Does this only become untranslatable when feature is
> "static call chains"?
In German, this might result in:
%<-mcall-ms2sysv-xlogues%> ist
mponent: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From cp/parser.c:
parser->type_definition_forbidden_message
= G_("types may not be defined in iterator type");
The term "may not" is ambiguous.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90148
--- Comment #5 from Roland Illig ---
From fortran/intrinsic.c:
gfc_warning_now (OPT_Wintrinsics_std, "The intrinsic %qs at %L is not "
"included in the selected standard but %s and %qs
will"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90176
Roland Illig changed:
What|Removed |Added
Attachment #46206|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90118
--- Comment #8 from Roland Illig ---
(In reply to Christophe Lyon from comment #7)
> Do you mean something like that?
>
> if p.startswith('-'):
> if len(p) >= 2 and (p[1].isalpha() and p != '-INF'):
: translation
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From call.c:
const char *msg = (msgstr == NULL
? ""
: ACONCAT ((msgstr, " ", NULL)));
inform (cloc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90118
--- Comment #5 from Roland Illig ---
(In reply to Christophe Lyon from comment #3)
> When running the script, it warned in 3 more occurrences in gcc/cp/call.c,
> which I updated too.
By reading the code, I think these instances are correct
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90152
--- Comment #1 from Roland Illig ---
(In reply to Roland Illig from comment #0)
> Instead of this comment, it would be better to pass the untranslated msgstr
> to print_z_candidate by enclosing the actual string literals with _(...).
Oops, I
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From aarch64.c:
if (aarch64_stack_protector_guard == SSP_SYSREG
&& !(opts->x_aarch64_stack_protector_guard_offset_str
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90176
Roland Illig changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
https://www.gnu.org/software/gcc/svnwrite.html says:
> If you already have an account on sourceware.org/gcc.gnu.org, ask
>
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
cc1 --help produces:
printf (" Known valid arguments for %s option:\n ", option->opt_text);
There's a _(...) missing around the string literal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79632
--- Comment #2 from Roland Illig ---
(In reply to Eric Gallager from comment #1)
> What exactly is the harm of the redundancy? I don't think this is too big of
> an issue...
The harm of redundancy is that there is no single point of truth. When
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90012
--- Comment #2 from Roland Illig ---
Thank you for changing this so quickly. Will your change make it into the next
translation round before the 9.1 release? That would be good because it would
save be quite some work.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90149
--- Comment #7 from Roland Illig ---
(In reply to Richard Biener from comment #6)
> IMNSHO the IL checker "errors" should continue to use GCC terms since they
> check the GIMPLE intermediate language. They also shouldn't necessarily be
>
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
Created attachment 46246
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46246=edit
linter for string literals
From engtype.c:
printf ("\t -D | --debug "
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90119
--- Comment #7 from Roland Illig ---
I didn't want to sound that harsh in my previous comment.
What I wanted to say is: to make the linter reliable and be able to handle the
full syntax of .po files, it's better to use an exising library that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90117
--- Comment #2 from Roland Illig ---
(In reply to Martin Liška from comment #1)
> Makes sense, I'll integrate that to our linter.
I've already integrated that into the linter, see the latest attachment in bug
90176.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90176
Roland Illig changed:
What|Removed |Added
Attachment #46234|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79183
--- Comment #9 from Roland Illig ---
Is there already someone who wants to fix the remaining messages?
Jakub, you fixed some of them already in
https://gcc.gnu.org/viewcvs?rev=258154=gcc=rev in March 2018.
There are still some messages that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90176
Roland Illig changed:
What|Removed |Added
Attachment #46212|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90119
--- Comment #6 from Roland Illig ---
(In reply to Martin Liška from comment #5)
> Thank you Roland for working on that. Can you please integrate your script
> with:
> contrib/check-internal-format-escaping.py
No, I cannot. Integrating it
Assignee: dmalcolm at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
from analyzer.opt:
- call tha would
+ call that would
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93659
--- Comment #1 from Roland Illig ---
And another typo, from the same file:
- Warn about code paths in which an initialized value is used.
+ Warn about code paths in which an uninitialized value is used.
: analyzer
Assignee: dmalcolm at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From analyzer.opt:
> Dump internal details about what the analyzer is doing to
> SRCFILE.analyzer.txt.
What is the analyzer doing to the SRCFILE? No harm, I hope.
(I do
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From darwin.opt:
> Loads all members of archive libraries
> The version of ld64 in use for this toolchain.
> Produce an output file that will bind symbols on load, rather th
Assignee: dmalcolm at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From analyzer.opts:
> fdump-analyzer-callgraph
> Common RejectNegative Var(flag_dump_analyzer_callgraph)
> Dump the analyzer supergraph to a SRCFILE.callgraph.dot file
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93694
--- Comment #1 from Roland Illig ---
double space:
> architecture \"name\"
unnecessarily verbose:
> Specify that the output file should be generated for architecture "name"
Why not simply: Generate output file for the named architecture.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93657
--- Comment #3 from Roland Illig ---
(In reply to David Malcolm from comment #2)
> Dump various analyzer internals to stderr.
I like these. They are simple and to the point, and I cannot find any ambiguity
anymore. :)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93659
--- Comment #5 from Roland Illig ---
Cool, thank you for the quick fix. That makes translating GCC more fun than in
the previous years. :)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93857
--- Comment #4 from Roland Illig ---
In the case of "boolean context", there are a few other diagnostics that also
contain these exact words. Therefore the tests should at least have enough
words to distinguish these diagnostics from the others.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93883
--- Comment #4 from Roland Illig ---
Just to clear up a potential misunderstanding. I do not want you to update
thousands of diagnostics. That would be a waste of time.
I only reported bugs for those diagnostics that I as the German translator
: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
This typo occurs 8 times in the GCC source tree.
It's only in the code, nothing user-visible. I just discovered it when I looked
at bug 93879.
In bb-reorder.c, there are several other typos in the same
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93857
--- Comment #3 from Roland Illig ---
(In reply to Jakub Jelinek from comment #2)
> testsuite/c-c++-common/Wint-in-bool-context.c
Thanks for pointing me to the test. My reasoning from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93883#c4 applies
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93879
--- Comment #2 from Roland Illig ---
(In reply to Jakub Jelinek from comment #1)
> The word quality looks correct, that is what is expected (profile quality is
> something like guessed_local, guessed, afdo, precise etc.), perhaps it
> should be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93859
--- Comment #2 from Roland Illig ---
(In reply to Jakub Jelinek from comment #1)
> git blame for the change which added the diagnostics and git log for that
> change should usually help to identify the test.
My strategy was simpler than "git
Component: sanitizer
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at
gcc dot gnu.org
Target Milestone
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93433
--- Comment #4 from Roland Illig ---
Reported as https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93433
The description of the Bugzilla component called "sanitizer" should be
corrected. Currently it reads as if I should report any libsanitizer bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93433
--- Comment #2 from Roland Illig ---
But why is there a bug category called sanitizer then, which even mentions
libsanitizer?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93433
--- Comment #7 from Roland Illig ---
(In reply to Martin Liška from comment #6)
> (In reply to Roland Illig from comment #4)
> > Reported as https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93433
> >
>
> Hello.
>
> You probably posted a wrong
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93797
--- Comment #1 from Roland Illig ---
Another typo: an extra space at the end
>"speculative call sequence ");
Another variable/diagnostic mismatch:
> error ("number of speculative targets %i mismatched with "
>
: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
3 times:
params.opt
ipa-visibility.c
gcc/tree.c
: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
CC: marxin at gcc dot gnu.org
Target Milestone: ---
In cgraph.c. The corresponding code has speculative_id, without the u.
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From tree-vrp.c:
> inform (DECL_SOURCE_LOCATION (rec), "defined here %qD", rec);
This should probably be "%qD was defined here".
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From c-common.c:
> warning_at (EXPR_LOCATION (expr), OPT_Wint_in_bool_context,
> "% using integer constants
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93852
--- Comment #1 from Roland Illig ---
> error ("virtual def operand missing for statement");
Curiously, the diagnostic a few lines above this one uses the correct word
"definition".
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93855
--- Comment #2 from Roland Illig ---
While here, the comment style should be made the same in
attr-access-read-write.c and attr-access-read-only.c. Currently, one file uses
/* block comments */ while the other uses // line-end comments.
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From tree-cfg.c:
> error ("missing % def");
The GCC diagnostics guidelines recomment to use actual words instead of
internal abbreviations.
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From tree-ssa-strlen.c:
> writing one too many bytes
The words "one bytes" don't match.
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From c-attribs.c:
> error ("attribute %qs positional argument %i value %wi exceeds "
>"number of function arguments %u",
The correct t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93857
--- Comment #1 from Roland Illig ---
I wrote a small example program, which I thought would trigger the diagnostic,
but it didn't do that in GCC 9.2.1.
int main(void) {
if (3 ? 4 : 5) {
return 1;
}
return 0;
}
gcc -Wall
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93855
--- Comment #4 from Roland Illig ---
(In reply to Andrew Pinski from comment #3)
> (In reply to Roland Illig from comment #2)
> > While here, the comment style should be made the same in
> > attr-access-read-write.c and attr-access-read-only.c.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93853
--- Comment #3 from Roland Illig ---
Thanks for the explanation.
Since there are many users of GCC who are not native English speakers, it might
make sense to avoid such complicated grammar. The GCC users should rather
concentrate on fixing
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From c-attribs.c:
> error ("attribute %qs invalid positional argument", attrstr);
This diagnostic is not covered by t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93855
--- Comment #1 from Roland Illig ---
In addition, I had expected that the %i placeholder were 1-based. From
attr-access-read-only.c:
> int RDONLY (4)
> rdonly_i_i_i_4 (int, int, int);
>// { dg-error "attribute 'access\\(read_only, 4\\)'
>
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From fortran/array.c:
> gfc_error ("rank + corank of %qs exceeds %d at %C", sym->name,
The other diagnostics in that file start with an uppercase letter.
201 - 300 of 531 matches
Mail list logo
