[Bug fortran/79860] i18n: single-word translation in "Character-valued %s %qs"

2017-03-15 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79860 --- Comment #2 from David Malcolm --- Author: dmalcolm Date: Wed Mar 15 18:05:06 2017 New Revision: 246170 URL: https://gcc.gnu.org/viewcvs?rev=246170&root=gcc&view=rev Log: Fix translation issue with character length * errors (PR fortran/79860)

[Bug fortran/79860] i18n: single-word translation in "Character-valued %s %qs"

2017-03-15 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79860 David Malcolm changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug preprocessor/80070] -Wmisleading-indentation disabled on -E (or when using distcc)

2017-03-16 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80070 --- Comment #1 from David Malcolm --- The warning is effective disabled when #line directives are present, in should_warn_for_misleading_indentation: /* Don't attempt to compare indentation if #line or # 44 "file"-style directives are pre

[Bug translation/80001] diagnostics: untranslateable %s placeholders in omp-offload.c

2017-03-21 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80001 --- Comment #4 from David Malcolm --- Author: dmalcolm Date: Tue Mar 21 16:26:09 2017 New Revision: 246326 URL: https://gcc.gnu.org/viewcvs?rev=246326&root=gcc&view=rev Log: omp-offload.c: translation fixes (PR translation/80001) gcc/ChangeLog:

[Bug translation/80001] diagnostics: untranslateable %s placeholders in omp-offload.c

2017-03-21 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80001 David Malcolm changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug translation/79423] Translation of warnings breaks IDE parsing of output

2017-03-23 Thread dmalcolm at gcc dot gnu.org
||2017-03-23 Assignee|unassigned at gcc dot gnu.org |dmalcolm at gcc dot gnu.org Target Milestone|--- |8.0 Ever confirmed|0 |1 --- Comment #4 from David Malcolm --- Discussion of this on the gcc mailing list

[Bug preprocessor/78836] ICE in get_source_location_for_substring, at input.c:1461

2017-03-24 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78836 David Malcolm changed: What|Removed |Added CC||dmalcolm at gcc dot gnu.org --- Comment

[Bug c/78732] Wrong description for Wendif-labels

2017-03-24 Thread dmalcolm at gcc dot gnu.org
||2017-03-24 CC||dmalcolm at gcc dot gnu.org Assignee|unassigned at gcc dot gnu.org |dmalcolm at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from David Malcolm --- Correct

[Bug translation/80055] do not mark internal compiler error messages for i18n

2017-03-24 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80055 --- Comment #4 from David Malcolm --- (In reply to Frederic Marchal from comment #2) > I suggest instead that internal messages be identified as such. Some other > messages begin with "Internal error". I would favor that solution for > messages n

[Bug c++/80177] wrong fixit hint for misspelled static_assert: __cpp_static_assert

2017-03-29 Thread dmalcolm at gcc dot gnu.org
||2017-03-29 CC||dmalcolm at gcc dot gnu.org Assignee|unassigned at gcc dot gnu.org |dmalcolm at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from David Malcolm --- Confirmed

[Bug c/78732] Wrong description for Wendif-labels

2017-03-31 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78732 --- Comment #2 from David Malcolm --- Author: dmalcolm Date: Fri Mar 31 14:24:27 2017 New Revision: 246616 URL: https://gcc.gnu.org/viewcvs?rev=246616&root=gcc&view=rev Log: Fix description of Wendif-labels (PR documentation/78732) gcc/c-family

[Bug c/78732] Wrong description for Wendif-labels

2017-03-31 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78732 David Malcolm changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c++/80177] wrong fixit hint for misspelled static_assert: __cpp_static_assert

2017-03-31 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80177 --- Comment #2 from David Malcolm --- Candidate patch: https://gcc.gnu.org/ml/gcc-patches/2017-03/msg01580.html

[Bug translation/80280] Missing closing quote (%>) c/semantics.c and c/c-typeck.c

2017-04-04 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80280 David Malcolm changed: What|Removed |Added CC||dmalcolm at gcc dot gnu.org --- Comment

[Bug tree-optimization/80318] GCC takes too much RAM and time compiling a template file

2017-04-05 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80318 David Malcolm changed: What|Removed |Added CC||dmalcolm at gcc dot gnu.org --- Comment

[Bug target/80377] gcc: error: unrecognized command line option ‘-mavx512’; did you mean ‘-mavx512 ’?

2017-04-09 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80377 --- Comment #1 from David Malcolm --- Thanks for filing this. Similar to PR c++/72786, and probably worked-around on trunk by r242965; presumably has a specific root-cause though.

[Bug c/82354] semi-colon instead of comma in parameter list produces confusing diagnostics

2017-09-28 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82354 --- Comment #2 from David Malcolm --- Note: the pertinent extension appears to be documented here: https://gcc.gnu.org/onlinedocs/gcc-7.2.0/gcc/Variable-Length.html#index-parameter-forward-declaration (see @cindex parameter forward declaration w

[Bug c/44515] improve message for missing ";"

2017-09-28 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44515 --- Comment #7 from David Malcolm --- The patch kit I proposed here: https://gcc.gnu.org/ml/gcc-patches/2017-09/msg01744.html and adds a fix-it hint and improves the location, making the successor token be a secondary location within the diagno

[Bug middle-end/82479] missing popcount builtin detection

2017-10-11 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82479 David Malcolm changed: What|Removed |Added CC||dmalcolm at gcc dot gnu.org --- Comment

[Bug c/81404] suggested hints for standard C macros should avoid GCC predefined macros

2017-10-11 Thread dmalcolm at gcc dot gnu.org
||2017-10-11 CC||dmalcolm at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from David Malcolm --- Thanks for filing this. Confirmed. Presumably we should print something like: a.c:1:9: error: ‘INT_MAX

[Bug c/7356] syntax errors immediately before an #include are reported for within the included file

2017-10-11 Thread dmalcolm at gcc dot gnu.org
at gcc dot gnu.org |dmalcolm at gcc dot gnu.org --- Comment #6 from David Malcolm --- Candidate patch: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82013

[Bug c/7356] syntax errors immediately before an #include are reported for within the included file

2017-10-11 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=7356 --- Comment #7 from David Malcolm --- (In reply to David Malcolm from comment #6) > Candidate patch: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82013 Oops; wrong link; correct link is: https://gcc.gnu.org/ml/gcc-patches/2017-10/msg00697.h

[Bug c/81404] suggested hints for standard C macros should avoid GCC predefined macros

2017-10-13 Thread dmalcolm at gcc dot gnu.org
at gcc dot gnu.org |dmalcolm at gcc dot gnu.org --- Comment #4 from David Malcolm --- Am working on this. Am not sure what is meant by comment #2 though; that sounds like a different issue.

[Bug c++/80567] bogus fixit hint for undeclared memset: else

2017-10-16 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80567 David Malcolm changed: What|Removed |Added CC||dmalcolm at gcc dot gnu.org --- Comment

[Bug c/81404] suggested hints for standard C macros should avoid GCC predefined macros

2017-10-17 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81404 --- Comment #5 from David Malcolm --- Candidate patch: https://gcc.gnu.org/ml/gcc-patches/2017-10/msg01083.html

[Bug bootstrap/82610] [8 Regression] Bootstrap fails on macOS 10.13 because of abort redefinition

2017-10-19 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82610 --- Comment #2 from David Malcolm --- Sorry about the breakage. (In reply to Richard Biener from comment #1) > Hmm, include/ shouldn't include system headers directly :/ Of course they > all do... > > is probably not too bad to include uncond

[Bug bootstrap/82610] [8 Regression] Bootstrap fails on macOS 10.13 and FreeBSD 11.1 because of abort redefinition

2017-10-23 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82610 --- Comment #5 from David Malcolm --- I posted fxcoudert's patch from comment 0 for review here: https://gcc.gnu.org/ml/gcc-patches/2017-10/msg01478.html

[Bug bootstrap/82610] [8 Regression] Bootstrap fails on macOS 10.13 and FreeBSD 11.1 because of abort redefinition

2017-10-23 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82610 --- Comment #6 from David Malcolm --- Author: dmalcolm Date: Mon Oct 23 20:25:58 2017 New Revision: 254024 URL: https://gcc.gnu.org/viewcvs?rev=254024&root=gcc&view=rev Log: Add INCLUDE_UNIQUE_PTR and use it (PR bootstrap/82610) gcc/ChangeLog:

[Bug bootstrap/82610] [8 Regression] Bootstrap fails on macOS 10.13 and FreeBSD 11.1 because of abort redefinition

2017-10-23 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82610 David Malcolm changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug middle-end/69976] Zero the local stack on function exit

2017-10-24 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69976 --- Comment #13 from David Malcolm --- Did this patch ever get posted to gcc-patc...@gcc.gnu.org? That's probably the best way to get some traction on this. Note that feature-freeze for GCC 8 is coming in the next few weeks, AIUI.

[Bug c/7356] syntax errors immediately before an #include are reported for within the included file

2017-10-25 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=7356 --- Comment #8 from David Malcolm --- Author: dmalcolm Date: Wed Oct 25 23:53:41 2017 New Revision: 254093 URL: https://gcc.gnu.org/viewcvs?rev=254093&root=gcc&view=rev Log: C: detect more missing semicolons (PR c/7356) c_parser_declaration_or_f

[Bug c/44515] improve message for missing ";"

2017-10-25 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44515 --- Comment #8 from David Malcolm --- Author: dmalcolm Date: Wed Oct 25 23:53:41 2017 New Revision: 254093 URL: https://gcc.gnu.org/viewcvs?rev=254093&root=gcc&view=rev Log: C: detect more missing semicolons (PR c/7356) c_parser_declaration_or_

[Bug c/7356] syntax errors immediately before an #include are reported for within the included file

2017-10-25 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=7356 David Malcolm changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c/44515] improve message for missing ";"

2017-10-25 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44515 --- Comment #9 from David Malcolm --- Trunk now emits: t.c: In function ‘foo’: t.c:4:8: error: expected ‘;’ before ‘}’ token bar() ^ ; t.c:7:1: } ~ (as of r253690, I believe). This improves the location for the diag

[Bug jit/82826] [8 regression] jit.dg test-benchmark.c.exe fail

2017-11-03 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82826 David Malcolm changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug jit/82826] [8 regression] jit.dg test-benchmark.c.exe fail

2017-11-03 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82826 --- Comment #2 from David Malcolm --- Candidate patch: https://gcc.gnu.org/ml/gcc-patches/2017-11/msg00238.html

[Bug jit/82826] [8 regression] jit.dg test-benchmark.c.exe fail

2017-11-06 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82826 --- Comment #3 from David Malcolm --- Author: dmalcolm Date: Mon Nov 6 16:31:04 2017 New Revision: 254458 URL: https://gcc.gnu.org/viewcvs?rev=254458&root=gcc&view=rev Log: ipa-fnsummary.c: fix use-after-free crash (PR jit/82826) gcc/ChangeLog

[Bug jit/82826] [8 regression] jit.dg test-benchmark.c.exe fail

2017-11-06 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82826 --- Comment #4 from David Malcolm --- Should be fixed by r254458.

[Bug jit/82826] [8 regression] jit.dg test-benchmark.c.exe fail

2017-11-06 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82826 David Malcolm changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug jit/82846] [8 regression] jit.dg test-alignment.c.exe, test-combination.c.exe, test-threads.c.exe fails

2017-11-06 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82846 --- Comment #2 from David Malcolm --- Works for me; I wasn't able to reproduce. Does the fix for PR jit/82826 (r254458) help? If I add this to set_options in harness.h: gcc_jit_context_set_bool_option ( ctxt, GCC_JIT_BOOL_OPTION_DUMP

[Bug c/82892] Spelling hints do not take into account missing compiler options (e.g. -fopenmp)

2017-11-08 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82892 --- Comment #2 from David Malcolm --- Thanks for filing this. I think a natural way to implement this would be on top of the deferred_diagnostic patch kit here, see e.g.: https://gcc.gnu.org/ml/gcc-patches/2017-11/msg00145.html (that one's sti

[Bug regression/83038] [8 regression] warning at random points in the input (array subscript -1 is below array bounds)

2017-11-17 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83038 David Malcolm changed: What|Removed |Added CC||dmalcolm at gcc dot gnu.org --- Comment

[Bug c/83056] GCC suggests the use of previously reported undeclared identifiers when reporting new undeclared identifiers

2017-11-20 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83056 David Malcolm changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug c/83056] GCC suggests the use of previously reported undeclared identifiers when reporting new undeclared identifiers

2017-11-20 Thread dmalcolm at gcc dot gnu.org
at gcc dot gnu.org |dmalcolm at gcc dot gnu.org

[Bug c++/72786] Odd spelling suggestion with later defined macro: Suggestion is identical to unknown identifier

2017-11-20 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72786 --- Comment #5 from David Malcolm --- Author: dmalcolm Date: Tue Nov 21 00:40:53 2017 New Revision: 254978 URL: https://gcc.gnu.org/viewcvs?rev=254978&root=gcc&view=rev Log: C++: provide macro used-before-defined hint (PR c++/72786) This patch

[Bug c/81404] suggested hints for standard C macros should avoid GCC predefined macros

2017-11-20 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81404 David Malcolm changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c++/80567] bogus fixit hint for undeclared memset: else

2017-11-20 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80567 --- Comment #3 from David Malcolm --- Author: dmalcolm Date: Tue Nov 21 00:50:39 2017 New Revision: 254980 URL: https://gcc.gnu.org/viewcvs?rev=254980&root=gcc&view=rev Log: C/C++: more stdlib header hints (PR c/81404) This patch extends the C

[Bug c/81404] suggested hints for standard C macros should avoid GCC predefined macros

2017-11-20 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81404 --- Comment #6 from David Malcolm --- Author: dmalcolm Date: Tue Nov 21 00:50:39 2017 New Revision: 254980 URL: https://gcc.gnu.org/viewcvs?rev=254980&root=gcc&view=rev Log: C/C++: more stdlib header hints (PR c/81404) This patch extends the C

[Bug preprocessor/81794] "would be stringified in traditional C" warning should be controlled by -Wtraditional

2017-11-20 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81794 --- Comment #5 from David Malcolm --- Author: dmalcolm Date: Tue Nov 21 00:57:29 2017 New Revision: 254981 URL: https://gcc.gnu.org/viewcvs?rev=254981&root=gcc&view=rev Log: Use -Wtraditional for "would be stringified in traditional C" (PR prepr

[Bug preprocessor/81794] "would be stringified in traditional C" warning should be controlled by -Wtraditional

2017-11-20 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81794 David Malcolm changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug c/83056] GCC suggests the use of previously reported undeclared identifiers when reporting new undeclared identifiers

2017-11-21 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83056 --- Comment #2 from David Malcolm --- Candidate patch: https://gcc.gnu.org/ml/gcc-patches/2017-11/msg01907.html

[Bug c++/81610] bogus fix-it hint for a call to an undeclared function: for

2017-11-21 Thread dmalcolm at gcc dot gnu.org
||2017-11-21 CC||dmalcolm at gcc dot gnu.org Assignee|unassigned at gcc dot gnu.org |dmalcolm at gcc dot gnu.org Ever confirmed|0 |1

[Bug c/83056] GCC suggests the use of previously reported undeclared identifiers when reporting new undeclared identifiers

2017-11-21 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83056 --- Comment #3 from David Malcolm --- Author: dmalcolm Date: Tue Nov 21 21:59:53 2017 New Revision: 255038 URL: https://gcc.gnu.org/viewcvs?rev=255038&root=gcc&view=rev Log: C: don't suggest names that came from earlier failures (PR c/83056) PR

[Bug c++/80177] wrong fixit hint for misspelled static_assert: __cpp_static_assert

2017-11-21 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80177 --- Comment #5 from David Malcolm --- Note: r247233 appears to have caused PR c++81610 and PR c++/80567. So if this is ever backported to gcc 7, we'd need the fix for those also.

[Bug c/83056] GCC suggests the use of previously reported undeclared identifiers when reporting new undeclared identifiers

2017-11-21 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83056 --- Comment #4 from David Malcolm --- Fixed on trunk for gcc 8 by r255038; not yet fixed on gcc-7-branch.

[Bug c++/62170] wrong quoting (and colors) for typedef diagnostics

2017-11-22 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62170 --- Comment #4 from David Malcolm --- Author: dmalcolm Date: Wed Nov 22 20:37:58 2017 New Revision: 255076 URL: https://gcc.gnu.org/viewcvs?rev=255076&root=gcc&view=rev Log: C/C++: fix quoting of "aka" typedef information (PR 62170) PR 62170 de

[Bug c++/62170] wrong quoting (and colors) for typedef diagnostics

2017-11-22 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62170 David Malcolm changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug tree-optimization/82583] missing -Warray-bounds on out-of-bounds inner indices

2017-11-22 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82583 --- Comment #5 from David Malcolm --- Author: dmalcolm Date: Wed Nov 22 21:12:36 2017 New Revision: 255082 URL: https://gcc.gnu.org/viewcvs?rev=255082&root=gcc&view=rev Log: jit: update test suite for change to -Warray-bounds jit.dg/test-error-

[Bug tree-optimization/82588] missing -Warray-bounds on a excessively large index

2017-11-22 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82588 --- Comment #6 from David Malcolm --- Author: dmalcolm Date: Wed Nov 22 21:12:36 2017 New Revision: 255082 URL: https://gcc.gnu.org/viewcvs?rev=255082&root=gcc&view=rev Log: jit: update test suite for change to -Warray-bounds jit.dg/test-error-

[Bug c/82050] [8 Regression] ICE on invalid code on x86_64-linux-gnu in column_range, at diagnostic-show-locus.c:1403

2017-11-23 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82050 --- Comment #3 from David Malcolm --- I attempted to copy&paste from comment #0, but couldn't reproduce the ICE (possibly a spaces vs tabs thing?) Jakub: please can you attach the reproducer file, and I'll take this. Thanks.

[Bug c/82050] [8 Regression] ICE on invalid code on x86_64-linux-gnu in column_range, at diagnostic-show-locus.c:1403

2017-11-23 Thread dmalcolm at gcc dot gnu.org
at gcc dot gnu.org |dmalcolm at gcc dot gnu.org --- Comment #5 from David Malcolm --- Thanks!

[Bug jit/83155] [8 regression] test-error-array-bounds.c.exe fail

2017-11-25 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83155 --- Comment #1 from David Malcolm --- I believe I fixed this in r255082.

[Bug middle-end/83164] [8 regression] internal compiler error: verify_gimple failed

2017-11-27 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83164 David Malcolm changed: What|Removed |Added CC||dmalcolm at gcc dot gnu.org --- Comment

[Bug middle-end/83164] [8 regression] internal compiler error: verify_gimple failed

2017-11-27 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83164 --- Comment #7 from David Malcolm --- BZ mangled the underline a bit in comment #6; the caret is on the '-' character, like this simplified version: thunk->callback = LHS - RHS; ^

[Bug c++/80567] bogus fixit hint for undeclared memset: else

2017-11-28 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80567 --- Comment #4 from David Malcolm --- Candidate patch: https://gcc.gnu.org/ml/gcc-patches/2017-11/msg02048.html

[Bug c++/81610] bogus fix-it hint for a call to an undeclared function: for

2017-11-28 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81610 --- Comment #2 from David Malcolm --- Candidate patch: https://gcc.gnu.org/ml/gcc-patches/2017-11/msg02048.html

[Bug c/82050] [8 Regression] ICE on invalid code on x86_64-linux-gnu in column_range, at diagnostic-show-locus.c:1403

2017-11-28 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82050 --- Comment #6 from David Malcolm --- Author: dmalcolm Date: Tue Nov 28 19:24:35 2017 New Revision: 255214 URL: https://gcc.gnu.org/viewcvs?rev=255214&root=gcc&view=rev Log: Reject fix-it hints for various awkward boundary cases (PR c/82050) PR

[Bug c/82050] [8 Regression] ICE on invalid code on x86_64-linux-gnu in column_range, at diagnostic-show-locus.c:1403

2017-11-28 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82050 David Malcolm changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c/82050] [8 Regression] ICE on invalid code on x86_64-linux-gnu in column_range, at diagnostic-show-locus.c:1403

2017-11-28 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82050 --- Comment #8 from David Malcolm --- Author: dmalcolm Date: Tue Nov 28 21:45:56 2017 New Revision: 255219 URL: https://gcc.gnu.org/viewcvs?rev=255219&root=gcc&view=rev Log: Handle very long lines when printing fix-it hints When fixing PR c/820

[Bug c/83236] "Did you mean" suggestions maybe shouldn't offer implementation-private names

2017-12-01 Thread dmalcolm at gcc dot gnu.org
||2017-12-01 Assignee|unassigned at gcc dot gnu.org |dmalcolm at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from David Malcolm --- Confirmed. Thanks for filing this.

[Bug c/83236] "Did you mean" suggestions maybe shouldn't offer implementation-private names

2017-12-01 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83236 --- Comment #2 from David Malcolm --- Candidate patch: https://gcc.gnu.org/ml/gcc-patches/2017-12/msg00066.html

[Bug c++/68810] [8 regression] FAIL: g++.dg/cpp0x/constexpr-reinterpret1.C -- test for errors -- -m32

2017-12-04 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68810 --- Comment #17 from David Malcolm --- (In reply to Jakub Jelinek from comment #16) > David, does your patchset solve this? The v2 version of the kit https://gcc.gnu.org/ml/gcc-patches/2017-11/msg00880.html doesn't affect it. The work-in-prog

[Bug c++/68810] [8 regression] FAIL: g++.dg/cpp0x/constexpr-reinterpret1.C -- test for errors -- -m32

2017-12-04 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68810 --- Comment #18 from David Malcolm --- ...but presumably a question here is "what is the ideal output of the compiler for that code?", and the answer might be: constexpr-reinterpret1.C:19:??: error: reinterpret_cast from integer to pointer {

[Bug c/83236] "Did you mean" suggestions maybe shouldn't offer implementation-private names

2017-12-04 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83236 --- Comment #4 from David Malcolm --- (In reply to Zack Weinberg from comment #3) > Maybe name_reserved_for_implementation_p should be a langhook? I'm only using it in the C/C++ frontends, and the implementation is identical for both, so I don't

[Bug c/83236] "Did you mean" suggestions maybe shouldn't offer implementation-private names

2017-12-04 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83236 --- Comment #6 from David Malcolm --- Ah, thanks. Indeed, and this stuff is highly FE specific.

[Bug c/83236] "Did you mean" suggestions maybe shouldn't offer implementation-private names

2017-12-06 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83236 --- Comment #7 from David Malcolm --- Author: dmalcolm Date: Wed Dec 6 20:02:55 2017 New Revision: 255453 URL: https://gcc.gnu.org/viewcvs?rev=255453&root=gcc&view=rev Log: C/C++: don't suggest implementation names as spelling fixes (PR c/83236

[Bug c/83236] "Did you mean" suggestions maybe shouldn't offer implementation-private names

2017-12-06 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83236 David Malcolm changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug tree-optimization/83336] New: Issues with displaying inlining chain for middle-end warnings

2017-12-08 Thread dmalcolm at gcc dot gnu.org
Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: dmalcolm at gcc dot gnu.org CC: msebor at gcc dot gnu.org Target Milestone: --- msebor reported this issue on the gcc-patches list

[Bug tree-optimization/83336] Issues with displaying inlining chain for middle-end warnings

2017-12-08 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83336 David Malcolm changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #1

[Bug c++/33952] -Wfatal-errors truncates multi-line error messages.

2016-09-06 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33952 David Malcolm changed: What|Removed |Added CC||dmalcolm at gcc dot gnu.org --- Comment

[Bug c/72858] incorrect fixit hints in -Wformat diagnostics

2016-09-12 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72858 --- Comment #2 from David Malcolm --- Author: dmalcolm Date: Mon Sep 12 16:01:02 2016 New Revision: 240095 URL: https://gcc.gnu.org/viewcvs?rev=240095&root=gcc&view=rev Log: Fix suggestions for non-trivial Wformat type cases (PR c/72858) gcc/c-

[Bug c/72858] incorrect fixit hints in -Wformat diagnostics

2016-09-12 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72858 --- Comment #3 from David Malcolm --- (In reply to David Malcolm from comment #2) > Author: dmalcolm > Date: Mon Sep 12 16:01:02 2016 > New Revision: 240095 The above commit fixes many of these issues; Martin identified some further improvements

[Bug middle-end/77672] wrong rich location in warning: writing a terminating nul past the end

2016-09-22 Thread dmalcolm at gcc dot gnu.org
||2016-09-22 Assignee|unassigned at gcc dot gnu.org |dmalcolm at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from David Malcolm --- To clarify: you want a substring_loc that uses the terminating nul character to use the

[Bug middle-end/77696] New: Confusing wording for -Wformat-length=

2016-09-22 Thread dmalcolm at gcc dot gnu.org
Assignee: unassigned at gcc dot gnu.org Reporter: dmalcolm at gcc dot gnu.org Target Milestone: --- Given this example from PR 77672... cat v.c && ./xgcc -B. -c v.c -Wall char d[3]; ex

[Bug bootstrap/77695] x86_64 bootstrap failure due to undeclared hook_uint_uintp_false

2016-09-22 Thread dmalcolm at gcc dot gnu.org
||2016-09-22 CC||dmalcolm at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from David Malcolm --- Confirmed. The patch here: https://gcc.gnu.org/ml/gcc-patches/2016-09/msg01620.html fixes it for me.

[Bug preprocessor/77672] wrong rich location in warning: writing a terminating nul past the end

2016-09-23 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77672 --- Comment #3 from David Malcolm --- Author: dmalcolm Date: Fri Sep 23 14:14:52 2016 New Revision: 240434 URL: https://gcc.gnu.org/viewcvs?rev=240434&root=gcc&view=rev Log: Provide location information for terminator characters (PR preprocessor

[Bug preprocessor/77672] wrong rich location in warning: writing a terminating nul past the end

2016-09-23 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77672 --- Comment #4 from David Malcolm --- (In reply to Martin Sebor from comment #2) > I think the general improvement I'm suggesting is to be able to put the > tilde(s) under or point the caret at any character of the format string, > including eith

[Bug preprocessor/77672] wrong rich location in warning: writing a terminating nul past the end

2016-09-23 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77672 --- Comment #5 from David Malcolm --- BTW, if you do have a need to send a "print the whole string" request via class substring_loc, that could be handled by passing in INT_MAX as the idx values, which will lead to a failure. (we could make it h

[Bug preprocessor/77672] wrong rich location in warning: writing a terminating nul past the end

2016-09-23 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77672 --- Comment #6 from David Malcolm --- Author: dmalcolm Date: Fri Sep 23 16:55:27 2016 New Revision: 240442 URL: https://gcc.gnu.org/viewcvs?rev=240442&root=gcc&view=rev Log: Fix gcc.dg/tree-ssa/builtin-sprintf-warn-4.c gcc/testsuite/ChangeLog

[Bug c++/77733] Add fixit hint suggesting to use std::move

2016-09-28 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77733 David Malcolm changed: What|Removed |Added CC||dmalcolm at gcc dot gnu.org --- Comment

[Bug c++/77733] Add fixit hint suggesting to use std::move

2016-09-28 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77733 --- Comment #4 from David Malcolm --- (In reply to Jonathan Wakely from comment #1) > As well as a fixit hint suggesting to use std::move it might be useful to > display the "" text in colour so it stands out. Good idea.

[Bug c++/77777] Use rich location to mark correct expression for "invalid use of non-static member function"

2016-09-28 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=7 David Malcolm changed: What|Removed |Added CC||dmalcolm at gcc dot gnu.org --- Comment

[Bug c++/77777] Use rich location to mark correct expression for "invalid use of non-static member function"

2016-09-28 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=7 --- Comment #4 from David Malcolm --- FWIW the location information is available in the frame above: Breakpoint 6, invalid_nonstatic_memfn_p (loc=205792, expr=, complain=3) at ../../src/gcc/cp/typeck.c:1834 1834ex

[Bug c++/77922] Bogus suggestion: ‘constexpr’ does not name a type; did you mean ‘constexpr’?

2016-10-11 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77922 --- Comment #3 from David Malcolm --- (In reply to Jakub Jelinek from comment #0) > constexpr int a = 1; > with -std=c++98 gives > pr.C:1:1: error: ‘constexpr’ does not name a type; did you mean ‘constexpr’? > constexpr int a = 1; > ^ >

[Bug other/78068] warning: implicit declaration of function ‘time’; did you mean ‘nice’? [-Wimplicit-function-declaration]

2016-10-21 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78068 --- Comment #3 from David Malcolm --- (In reply to Markus Trippelsdorf from comment #2) > (In reply to Andrew Pinski from comment #1) > > time declaration really is not present in the preprocessed source file. I > > can't seem to figure out why

[Bug driver/78196] [7 Regression] GCC self-test breaks native Windows x86 builds

2016-11-03 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78196 --- Comment #2 from David Malcolm --- Sorry for the breakage. There seem to be two parts to this bug: (a) allow building with /dev/null on Windows, by having the driver pick a better name for the .s file. ( https://msdn.microsoft.com/en-us/lib

[Bug target/78213] [7 Regression] -fself-test fails on aarch64

2016-11-10 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78213 --- Comment #6 from David Malcolm --- (In reply to Aldy Hernandez from comment #5) > Confirmed with a cross build with: > > cat >a.c < int i; > void bar();

[Bug c++/78313] [7 Regression] Misleading spelling suggestion

2016-11-11 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78313 --- Comment #2 from David Malcolm --- Thanks. Has some similarities to PR 77922.

[Bug preprocessor/78324] New: Valgrind issues seen with gcc.dg/tree-ssa/builtin-sprintf-2.c

2016-11-11 Thread dmalcolm at gcc dot gnu.org
Priority: P3 Component: preprocessor Assignee: unassigned at gcc dot gnu.org Reporter: dmalcolm at gcc dot gnu.org Target Milestone: --- Seen on x86_64 with r242065. $ ./xgcc -B. -c ../../src/gcc/testsuite/gcc.dg/tree-ssa/builtin-sprintf-2.c -O2 -fprintf-return-value

[Bug c++/77922] Bogus suggestion: ‘constexpr’ does not name a type; did you mean ‘constexpr’?

2016-11-14 Thread dmalcolm at gcc dot gnu.org
||2016-11-14 Assignee|unassigned at gcc dot gnu.org |dmalcolm at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #5 from David Malcolm --- Confirmed. I'm working on a fix.

<    10   11   12   13   14   15   16   17   18   19   >