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

2023-04-12 Thread roland.illig at gmx dot de via Gcc-bugs
Component: modula2 Assignee: gaius at gcc dot gnu.org Reporter: roland.illig at gmx dot de Target Milestone: --- wrong: > libraries maybe correct: > libraries may be

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

2023-03-27 Thread roland.illig at gmx dot de via Gcc-bugs
: unassigned at gcc dot gnu.org Reporter: roland.illig at gmx dot de CC: marxin at gcc dot gnu.org Target Milestone: --- 3 times

[Bug modula2/109315] New: typo: inconsistant

2023-03-28 Thread roland.illig at gmx dot de via Gcc-bugs
Component: modula2 Assignee: gaius at gcc dot gnu.org Reporter: roland.illig at gmx dot de Target Milestone: --- m2decl.cc says: > inconsistant That should be 'inconsistent'.

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

2023-03-28 Thread roland.illig at gmx dot de via Gcc-bugs
Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: roland.illig at gmx dot de Target Milestone: --- fortran/openmp.cc says: > Invalid combined or composit directive 'composit' should probably be 'composite'. There is no test case for this diagnostic.

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

2023-03-27 Thread roland.illig at gmx dot de via Gcc-bugs
Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: roland.illig at gmx dot de Target Milestone: --- In cp/contracts.cc, check_postcondition_result says: > error_at (loc, "%s does not return a value to test", what); At that point, 'what' co

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

2023-06-14 Thread roland.illig at gmx dot de via Gcc-bugs
Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: roland.illig at gmx dot de Target Milestone: --- ~~~c enum e { e1, e2, }; int side_effect(void); enum e demo(_Bool, enum e); enum e demo(_Bool cond, enum e c1

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

2023-05-18 Thread roland.illig at gmx dot de via Gcc-bugs
Assignee: unassigned at gcc dot gnu.org Reporter: roland.illig at gmx dot de Target Milestone: --- https://github.com/NetBSD/src/blob/93dc650849c98c54c31aa9cbbce9affaaf649563/bin/cat/cat.c#L185 has misleading indentation, as the 'else' branch does not start with a '{'. I tried

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

2023-07-21 Thread roland.illig at gmx dot de via Gcc-bugs
Assignee: unassigned at gcc dot gnu.org Reporter: roland.illig at gmx dot de Target Milestone: --- Target: arm Created attachment 55598 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55598=edit precompiled code that generates unrelated diagnostics In NetBS

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

2023-07-21 Thread roland.illig at gmx dot de via Gcc-bugs
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=edit precompiled code that works as intended

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

2023-07-22 Thread roland.illig at gmx dot de via Gcc-bugs
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

2023-07-22 Thread roland.illig at gmx dot de via Gcc-bugs
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=edit Preprocessed source from comment 5

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

2023-07-22 Thread roland.illig at gmx dot de via Gcc-bugs
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':

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

2023-07-22 Thread roland.illig at gmx dot de via Gcc-bugs
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

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

2023-06-20 Thread roland.illig at gmx dot de via Gcc-bugs
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

2023-06-20 Thread roland.illig at gmx dot de via Gcc-bugs
Component: c Assignee: unassigned at gcc dot gnu.org Reporter: roland.illig at gmx dot de Target Milestone: --- ~~~c typedef typeof(sizeof 0) size_t; int memcmp(const void *, const void *, size_t); int demo(const char *); int demo(const char *p) { const char *start = p

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

2023-07-02 Thread roland.illig at gmx dot de via Gcc-bugs
: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: roland.illig at gmx dot de Target Milestone: --- ~~~c struct symbol { struct symbol *next; }; void f(const struct symbol *sym) { for (const struct symbol

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

2023-06-20 Thread roland.illig at gmx dot de via Gcc-bugs
Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: roland.illig at gmx dot de Target Milestone: --- ~~~c #include #include static void __attribute__((__format__(__printf__, 1, 2))) my_printf(const char

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

2024-01-10 Thread roland.illig at gmx dot de via Gcc-bugs
: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: roland.illig at gmx dot de Target Milestone: --- Target: vax Created attachment 57035 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57035=e

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

2024-01-11 Thread roland.illig at gmx dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113324 Roland Illig changed: What|Removed |Added Resolution|--- |FIXED Status|WAITING

[Bug driver/114082] Guidelines for options are empty

2024-02-23 Thread roland.illig at gmx dot de via Gcc-bugs
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

2024-02-23 Thread roland.illig at gmx dot de via Gcc-bugs
Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: roland.illig at gmx dot de Target Milestone: --- Target: riscv riscv.opts says: > mmovcc > Target Var(TARGET_MOVCC) > Enable conditional moves uncond

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

2024-02-23 Thread roland.illig at gmx dot de via Gcc-bugs
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 preprocessor/114082] New: Guidelines for options are empty

2024-02-23 Thread roland.illig at gmx dot de via Gcc-bugs
Component: preprocessor Assignee: unassigned at gcc dot gnu.org Reporter: roland.illig at gmx dot de Target Milestone: --- https://gcc.gnu.org/onlinedocs/gccint/Guidelines-for-Options.html The section is empty, and it has been so since its creation in 2018. When I

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

2024-03-17 Thread roland.illig at gmx dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114364 --- Comment #3 from Roland Illig --- The diff looks good to me. Untested.

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

2024-03-18 Thread roland.illig at gmx dot de via Gcc-bugs
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'

2024-03-16 Thread roland.illig at gmx dot de via Gcc-bugs
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'

2024-03-16 Thread roland.illig at gmx dot de via Gcc-bugs
Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: roland.illig at gmx dot de Target Milestone: --- >From c-family/c-omp.cc: > error_at (LOCATION_OR (eloc, loc), > "variable %qD used %s is bound " >

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

2024-03-20 Thread roland.illig at gmx dot de via Gcc-bugs
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

2024-03-20 Thread roland.illig at gmx dot de via Gcc-bugs
Component: target Assignee: unassigned at gcc dot gnu.org Reporter: roland.illig at gmx dot de Target Milestone: --- Target: loongarch "enabing %qs promotes %<%s%s%> to %<%s%s%>" Should be "enabling".

[Bug rust/114629] New: rust-ast-resolve-expr contains bloated code for funny_error

2024-04-07 Thread roland.illig at gmx dot de via Gcc-bugs
Priority: P3 Component: rust Assignee: unassigned at gcc dot gnu.org Reporter: roland.illig at gmx dot de CC: dkm at gcc dot gnu.org, gcc-rust at gcc dot gnu.org Target Milestone: --- The file contains funny_error, which unnecessarily bloats

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

2024-03-04 Thread roland.illig at gmx dot de via Gcc-bugs
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

<    1   2   3   4   5   6