https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77696
Richard Biener changed:
What|Removed |Added
Target Milestone|9.5 |---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77696
Richard Biener changed:
What|Removed |Added
Target Milestone|9.4 |9.5
--- Comment #21 from Richard Biener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77696
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|9.3 |9.4
--- Comment #20 from Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77696
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|9.2 |9.3
--- Comment #19 from Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77696
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|9.0 |9.2
--- Comment #18 from Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77696
--- Comment #17 from David Malcolm ---
Prototype of a new approach posted here:
"[PATCH 0/5] RFC: gimple-ssa-sprintf.c: a new approach (PR middle-end/77696)"
https://gcc.gnu.org/ml/gcc-patches/2018-09/msg00771.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77696
Manuel López-Ibáñez changed:
What|Removed |Added
CC||manu at gcc dot gnu.org
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77696
--- Comment #15 from David Malcolm ---
(In reply to David Malcolm from comment #14)
Some random UI ideas (brainstorming in Emacs, so no idea if these are
*good* ideas):
warning: buffer overflow: writing 9-110 bytes into a buffer with capacit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77696
--- Comment #14 from David Malcolm ---
Another example from Martin:
extern char buf[80];
extern char tmpdir[80];
extern char fname[8];
void f (int num)
{
sprintf (buf, "/%s/%s-%i.tmp", tmpdir, fname, num);
}
In the most
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77696
--- Comment #13 from David Malcolm ---
Some more examples to consider (thanks Martin):
struct MyStrings {
char a[8], b[20];
};
const struct MyStrings ms[] = {
{ "foo", "bar" }, { "abcd", "klmno" }, ...
};
Consider:
s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77696
--- Comment #12 from David Malcolm ---
(In reply to David Malcolm from comment #5)
> I brainstormed some ideas on making these kinds of warning easier for
> the user to understand.
Copying a string to a buffer allocated with strlen(), rather tha
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77696
--- Comment #11 from David Malcolm ---
(In reply to David Malcolm from comment #5)
> I brainstormed some ideas on making these kinds of warning easier for
> the user to understand.
A simple example where the overflowing write is to the start of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77696
--- Comment #10 from David Malcolm ---
(In reply to David Malcolm from comment #5)
> I brainstormed some ideas on making these kinds of warning easier for
> the user to understand.
Here's another possible visualization, of a different overflow:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77696
--- Comment #9 from David Malcolm ---
(In reply to David Malcolm from comment #8)
> (In reply to David Malcolm from comment #5)
> > I brainstormed some ideas on making these kinds of warning easier for
> > the user to understand.
>
> Getting rea
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77696
--- Comment #8 from David Malcolm ---
(In reply to David Malcolm from comment #5)
> I brainstormed some ideas on making these kinds of warning easier for
> the user to understand.
Getting really fancy, we could emit an ASCII art visualization to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77696
--- Comment #7 from David Malcolm ---
(In reply to David Malcolm from comment #6)
A tweak to this would be to show the point where the overflow occurs
(if the substring location code is up to it...):
demo.c: In function ‘test_2’:
demo.c:6:23: w
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77696
--- Comment #6 from David Malcolm ---
(In reply to David Malcolm from comment #5)
> I brainstormed some ideas on making these kinds of warning easier for
> the user to understand.
We could use the new labeling-of-source-ranges idea from:
https
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77696
--- Comment #5 from David Malcolm ---
(In reply to David Malcolm from comment #4)
> In the meantime, I'm going to post some of the other UI ideas for this that
> we've being chatting about, so that they're captured publicly.
Consider this proble
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77696
David Malcolm changed:
What|Removed |Added
Status|WAITING |ASSIGNED
Assignee|msebor at gc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77696
Martin Sebor changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #3 from Martin Sebor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77696
Martin Sebor changed:
What|Removed |Added
Summary|Confusing wording for |Confusing wording for
|
21 matches
Mail list logo
