Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
from tree.c:
error ("type variant differs by " #flag ".");
This diagnostic is no
iority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
from config/nios2/nios2.c:
error ("`custom-%s=' argument requires "
"numeric digits", N2FPU_NAME (code));
"numeric di
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
from config/arc/arc.c:
warning (DK_WARNING,
"PIC is not supported for %s. Generating non-PIC code only..",
arc_cpu_string);
The two periods
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79868
--- Comment #5 from Roland Illig ---
Same for all occurrences of the »pragma_or_attr« variable.
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
from params.def:
DEFPARAM(PARAM_VECT_MAX_PEELING_FOR_ALIGNMENT,
"vect-max-peeling-for-alignment",
"Max numbe
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
from omp-offload.c:
error_at (loop->loc,
"%s uses same OpenACC parallelism as containing loop",
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80001
--- Comment #1 from Roland Illig ---
Note that the above is not the only instance. Please check each %s format
specifier in this file for this pattern.
loop->routine ? "routine call" : "loop" (twice)
tiling ? " tile" : ""
While here, please
: translation
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
from config/i386/386.c:
error ("interrupt service routine should have unsigned %s"
"int as the second argument",
TARGET_64BIT
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
from simple-ssa-sprintf.c:
The block after "if (res.min == res.max)" has the following expression:
const char* fmtstr
nent: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
from gimple-ssa-sprintf.c:
warning_at (gimple_location (info.callstmt), info.warnopt (),
"specified bound %wu exceeds %",
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79997
--- Comment #1 from Roland Illig ---
Another instance in the same file, function format_directive:
1 == fmtres.range.likely
And another, in the same function:
min == 1
: translation
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
from gimple.c:
error_at (OMP_CLAUSE_LOCATION (source_c),
"%<depend(source)%> clause specified together with "
"%<depend(sink
Priority: P3
Component: ipa
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
from ipa-devirt.c:
if (warning_at (
DECL_SOURCE_LOCATION(TYPE_NAME (DECL_CONTEXT (vtable->decl))),
OPT_Wodr,
&
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79855
Roland Illig changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79855
--- Comment #5 from Roland Illig ---
Here is a simple program to check the help strings for consistency:
#include
#include
static void assert_trailing_dot(const char *help)
{
size_t len = strlen(help);
if (len > 0 &&
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79858
--- Comment #2 from Roland Illig ---
What about the letters "mode"? Are they to be translated? Or should the
resulting text, even in Arabic, be "QImode"?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79857
--- Comment #3 from Roland Illig ---
Assuming that the diagnostics containing words like "edge" or "BB" are
presented to the GCC user, how are they going to make any use of them?
Or "cgraph_node has wrong clone_of"? As a programmer, I have no
NCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
from c-family/c-indentation.c:
if (warning_at (guard_tinfo.location, OPT_Wmisleading_i
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
In config/aarch64/aarch64.c, the function aarch64_err_no_fpadvsimd assembles
diagnostics using plain string concatenation, leaving some
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
from config/aarch64/aarch64.c:
error ("invalid feature modifier in -mcpu=%qs", str);
The quotes should be around »-mcpu=given-value«, not around
-mcpu=»given-value«.
: target
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
from config/nds32/nds32.c:
sorry ("not support -fpic");
As the German translator, am I supposed to translate this with incorrect
grammar? Since I don't know
ty: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
from c-family/c-warn.c:
warning_at_rich_loc_n (, OPT_Wrestrict, arg_positions.length (),
"pass
: other
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
Most diagnostics don't end with a period. But some do. Most of them can be
found using this perl-compatible regular expression:
\b(warning|warning_at|error)\s
ty: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
from config/i386/i386.c:
sorry ("%s instructions aren't allowed in %s service routine",
isa, (cfun
: target
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
As a translator, I currently have this (from config/arc/arc.c):
operand %d should be a 6 bit unsigned immediate
operand %d should be a 8 bit unsigned immediate
operand %d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79871
--- Comment #2 from Roland Illig ---
Thanks for the explanation. This leaves open the %s.
Looking further in the code, I can see that %s is either the string "constant"
or the string "lane". In other diagnostics, these words are usually
3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
from config/avr/avr.c:
const char *isr = cfun->machine->is_interrupt ? "interrupt" : "signal";
warning_at (loc, OPT_Wm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79883
--- Comment #2 from Roland Illig ---
Quoting myself from bug 79868:
Although "interrupt" and "signal" are both keywords in the language, they are
not used as such in this diagnostic. Rather, they form part of the normal
sentence structure.
For
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
from read-rtl-function.c:
error ("duplicate insn UID: %i", INSN_UID (insn));
As an i18n translator, I'm n
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79868
--- Comment #4 from Roland Illig ---
(In reply to Richard Earnshaw from comment #3)
> Both pragma and attribute are keywords in the language. If the substituted
> value were placed in quotes, would that help?
No, it wouldn't. It would only
ty: normal
Priority: P3
Component: driver
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
from opts.c:
error_at (loc,
"unrecognized argument to -f%ssanitize%s= option: %q.*s;"
" did you
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
from config/arm/arm.c:
error ("%K%s %wd out of range %wd - %wd",
As a translator I have no idea what the first two placeholders are and why they
are written witho
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79868
--- Comment #2 from Roland Illig ---
Also, the word "attribute" appeared as an untranslated literal:
ret = aarch64_process_target_attr (args, "attribute");
This makes it impossible to do any proper translation into any language other
than
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
from config/arc/arc.c:
error ("%s is not available for %s architecture",
DOC, arc_selected_cpu->arch_info->name);
As a translator, I have no idea what
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
As detailed in PR/79596, as a translator I don't see any value in translating
internal compiler error messages.
The messages in symtab_node
ty: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
from config/aarch64/aarch64.c:
error ("malformed target %s value", pragma_or_attr);
Assuming that the %s place
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79868
--- Comment #1 from Roland Illig ---
Same for:
error ("target %s %qs is invalid", pragma_or_attr, token);
: other
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
In config/aarch64/aarch64.c I found this code:
error ("%Klane %wd out of range %wd - %wd", exp, lane, low, high - 1);
It seems wrong to me that there is no s
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
In tree-cfg.c, the function verify_gimple_assign_single reports several errors
that cannot be triggered by ordinary GCC users
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79845
--- Comment #5 from Roland Illig ---
Thank you very much. The patch looks great.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79856
Roland Illig changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79883
Roland Illig changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79868
--- Comment #8 from Roland Illig ---
Yes, the patch looks good to me. (I didn't even catch the one instance that
Frederic found.) Thanks for putting this much effort into this issue.
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
Specify use soft floating point ABI which mean alias to -mabi=2.
Specify use soft floating point ABI which mean alias to -mabi=2fp+.
Specify a fpu configuration value from 0 to 7; 0-3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85665
--- Comment #1 from Roland Illig ---
To give a bit of context: All these typos have been introduced after b20180401,
which gives them only very little time to be discovered.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85665
--- Comment #3 from Roland Illig ---
(In reply to Jonathan Wakely from comment #2)
> It might be better to report multiple bugs, one per target backend, so that
> the relevant target maintainers are informed.
Oh, I tried that last year. Of the
at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
While translating gcc-8.1-b20180128 into German, I discovered the following
typos:
switch statements, which use
=> "statements, which" should be replaced with "statements that"
what to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79644
Roland Illig changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47105
Roland Illig changed:
What|Removed |Added
CC||roland.illig at gmx dot de
--- Comment
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
In English, the following idiom is correct:
warning_at (loc, opt,
(integer_onep (range[0])
? G_("%K%qD writing %E
ty: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
* There are two spaces in a row
* Enforcement has 3 e's.
nt: target
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From config/arc/arc.c:
warning (DK_WARNING,
"PIC is not supported for %s. Generating non-PIC code only..",
arc_cpu_string);
There ca
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85267
Roland Illig changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80021
--- Comment #2 from Roland Illig ---
*** Bug 85267 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85267
--- Comment #2 from Roland Illig ---
Exact duplicate of #80021, which was just missing the keyword
"verify_variant_match".
: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From tree.c:
#define verify_variant_match(flag) \
do
mponent: c
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
In c-family/c-warn.c:
else if (DECL_DECLARED_INLINE_P (olddecl)
&& DECL_UNINLINABLE (newdecl)
&& lookup_attribute ("noin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84911
--- Comment #1 from Roland Illig ---
While here, please move the "target(\"arch=\")" out of the string to be
translated, to eliminate any possibility of the translator making
copy-and-paste mistakes.
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
In gcc/c-warn.c:
warning_at (loc, OPT_Wconversion,
"conversion from %qT to to %qT discards imaginary "
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
In aarch64.c:
error ("invalid name (\"%s\") in %<target(\"arch=\")%> pragma or
attribute", str);
Please use %qs instead of "%s"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80055
--- Comment #9 from Roland Illig ---
(In reply to Frederic Marchal from comment #8)
> Two years later, I appear to be the only active translator. I translated all
> the messages. So, cutting down the number of messages is not an issue I feel
>
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
error ("invalid regular expression '%s' in %<%s%>",
Please implement a GCC-specific linter that prohibits single quotes in
messages. These should either be %' i
: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From fortran/expr.c:
gfc_error ("Assumed shape array %qs at %L is not permitted "
"in an initialization expression",
gfc_error ("Assu
Priority: P3
Component: translation
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
from fortran/frontend-passes.c:
#define B_ERROR(n) _("Incorrect extent in argument B in MATMUL intr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89936
--- Comment #1 from Roland Illig ---
And just in case the punctuation in this particular message is fully
intentional: Please document it why it needs to be exactly this way. It looks
too much like a mistake.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40883
--- Comment #5 from Roland Illig ---
I wouldn't classify bug 89936 as trivial as it strongly recommends to write a
linter, and that might take a while. Especially since the GCC project seems to
avoid these consistency linters; at least that's my
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79878
--- Comment #1 from Roland Illig ---
Two years later, nothing has changed.
As the German translator, I refuse to translate these messages. There is really
nothing a GCC user could take away from a message like "incorrect entry in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89936
--- Comment #2 from Roland Illig ---
Just as a reference, I wrote a little linter just for fun 2 years ago. Since it
was February 2017, it was most likely targeted at GCC 7.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79842
--- Comment #3 from Roland Illig ---
Any progress on this one? To me it sounds like it were quite easy to fix.
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
DEFPARAM (PARAM_GRAPHITE_MAX_NB_SCOP_PARAMS,
"graphite-max-nb-scop-params",
"Maximum number of parameters in a SCoP.",
10, 0, 0)
/* Max
: translation
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
As of 2019-04-01, the params.def looks as if it has been written by many
different authors with no coordination:
* some parameter descriptions start with "The&quo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89915
--- Comment #2 from Roland Illig ---
(In reply to Andrew Pinski from comment #1)
> params should be considered as internal options
When I read the above, I first thought: Yay, less strings for me to translate.
Just exclude them from gcc.pot.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80058
--- Comment #1 from Roland Illig ---
Before fixing these bugs, the program that checks these instances should be
checked in and be run each time before the GCC code is sent to the translators.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40883
--- Comment #2 from Roland Illig ---
I don't know how to add these bugs to the "Depends on" field, therefore I'm
listing them here. Could it be that a mere reporter cannot do this?
bug 79645
bug 79646
bug 79846
bug 79858
bug 79869
bug 79870
bug
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79618
--- Comment #5 from Roland Illig ---
Agreed.
I myself cannot remove it from the list of trivial bugs though.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89936
--- Comment #6 from Roland Illig ---
Thank you very much.
nt: target
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
risvc.c:
error ("%qs function cannot have different intterupt type.", "interrupt");
intterupt should be interrupt
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
Please teach the diagnostics linter to reject the following code from
cp/typeck2.c:
pedwarn (loc, OPT_Wnarrowing,
"narrowing conversion of %qE fro
Assignee: ibuclaw at gdcproject dot org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From expressionsem.c:
const char *p = v->isParameter() ? "parameter" : "local";
e->error("cannot take address of scope %s %s in @safe function %s&
: ibuclaw at gdcproject dot org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
The GCC standard for diagnostics is:
* placeholders are quoted: use %qs instead of a simple %s
* quotes are written % instead of `this' or `this` or 'this' or
"this" or similar varia
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From aarch64.opt:
-msve-vector-bits= Set the number of bits in an SVE vector
register to N.
In a previous version, the text
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89939
--- Comment #3 from Roland Illig ---
Would it be possible to teach exgettext that inside the _(...), the only
allowed tokens are string literals, and maybe the PRIU64 constants? There's
probably some more tokens that I just forgot, but a test
Priority: P3
Component: translation
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From rs6000.h:
:%eMissing -mcpu option in ASM_CPU_SPEC?\n} \
I thought there were a linter checking that each option
Priority: P3
Component: translation
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
There are the following msgids:
bad value %qs for %<-mtrap-precision%> switch
bad value %qs for %<-mfp-rounding-mode%> swit
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From aarch64.c:
error ("incompatible options %<-mstack-protector-guard=global%> and"
"%<-mstack-p
lation
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
In most cases %<%s%> is equivalent to the simpler %qs, therefore the latter
should be used consistently.
Surprisingly there is one exception in error.c, which is already wel
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79869
--- Comment #1 from Roland Illig ---
ping? Two years later, and I still don't know how to translate this string into
proper German.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79183
Roland Illig changed:
What|Removed |Added
CC||roland.illig at gmx dot de
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90121
--- Comment #1 from Roland Illig ---
Same for:
error ("unknown CRIS cpu version specification in %<-mtune=%> : %s",
cris_tune_str);
: translation
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From arc.c:
error ("Option %s=%s is not available for %s CPU.", \
DOC0, DOC1, arc_selected_cpu->name); \
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From cris.c:
error ("unknown CRIS version specification in %<-march=%> or "
"%<-mcpu=%> : %s", cris_cpu_str);
The space before the colon is too much.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90119
--- Comment #1 from Roland Illig ---
Next example from avr.c:
%<-fpic%> is not supported
%<-fPIC%> is not supported
%<-fpie%> is not supported
%<-fPIE%> is not supported
Priority: P3
Component: debug
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From opts.c:
case OPT_gdwarf:
if (arg && strlen (arg) != 0)
{
error_at (loc, "%<-gdwarf%
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From
https://github.com/NetBSD/pkgsrc/blob/342fd468170/lang/gcc8/patches/patch-gcc_configure:
--- gcc/configure.orig 2015-09-30 23:06:11.0 +
+++ gcc/configure
@@ -28321,7 +28321,7
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
From float2.c:
#if 1
/* This is ifdef'd out for now. long double support under SunOS/gcc
is pretty much non-existent. You'll get the odd bus error in library
This is an obvious
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90152
--- Comment #3 from Roland Illig ---
(In reply to Martin Sebor from comment #2)
> Just so I'm clear: what exactly needs to be enclosed in _(...) in
> print_z_candidate?
The code:
print_z_candidate (loc, "candidate:", candidates);
should
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90251
--- Comment #2 from Roland Illig ---
I posted an updated version of the linter to bug 79618, and I will post further
updates only there.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79618
--- Comment #7 from Roland Illig ---
Created attachment 46269
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46269=edit
linter for string literals
The attached linter detects:
* multiline string literals that have the space at the start
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90118
--- Comment #9 from Roland Illig ---
The particular issue has been fixed, the linter has been updated in bug 90176,
therefore I think this bug can be closed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90149
--- Comment #10 from Roland Illig ---
(In reply to Richard Biener from comment #9)
> IMHO the error calls in our IL checkers are abusive, they could have been
> simple dumps to stderr for example. It was just "convenient" to use
> a disagnostic
101 - 200 of 531 matches
Mail list logo
