[Bug middle-end/87757] weird underlining and colors in sprintf warnings for unterminated arrays

2018-10-30 Thread aldyh at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87757 Aldy Hernandez changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug middle-end/87757] weird underlining and colors in sprintf warnings for unterminated arrays

2018-10-26 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87757 --- Comment #4 from David Malcolm --- Aldy: do you remember why the arguments need to have the same location as the call itself? The first case works because during gimplify_arg it's wrapped in a NOP_EXPR which is casting from char[] to char *,

[Bug middle-end/87757] weird underlining and colors in sprintf warnings for unterminated arrays

2018-10-26 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87757 --- Comment #3 from David Malcolm --- prior to that gimplify.c code, the location of the argument is correctly set, as: t.c:8:31: note: 8 | __builtin_sprintf (e, "%s", [0]); | ^

[Bug middle-end/87757] weird underlining and colors in sprintf warnings for unterminated arrays

2018-10-26 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87757 David Malcolm changed: What|Removed |Added CC||aldyh at gcc dot gnu.org --- Comment #2

[Bug middle-end/87757] weird underlining and colors in sprintf warnings for unterminated arrays

2018-10-25 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87757 Martin Sebor changed: What|Removed |Added Keywords||diagnostic CC|