https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70481
--- Comment #7 from Jonathan Wakely ---
For the record, this was fixed for 4.9.4, 5.4.0, 6.1.0 and later.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70481
--- Comment #6 from Jakub Jelinek ---
Author: jakub
Date: Thu May 19 12:05:41 2016
New Revision: 236456
URL: https://gcc.gnu.org/viewcvs?rev=236456&root=gcc&view=rev
Log:
Backported from mainline
2016-05-19 Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70481
--- Comment #5 from Jakub Jelinek ---
Author: jakub
Date: Thu May 19 10:44:31 2016
New Revision: 236452
URL: https://gcc.gnu.org/viewcvs?rev=236452&root=gcc&view=rev
Log:
Backported from mainline
2016-05-19 Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70481
Jeffrey A. Law changed:
What|Removed |Added
CC||brian.carpenter at gmail dot
com
--- C
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70481
Jeffrey A. Law changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70481
--- Comment #2 from Marcel Böhme ---
These are two distinct bugs. During fuzzing the btypevec bug appears more
often. But it seemed less critical since only NULL is written to the freed
memory:
work -> btypevec[ret] = NULL;
On the other hand, th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70481
Mikhail Maltsev changed:
What|Removed |Added
CC||miyuki at gcc dot gnu.org
--- Comment
