https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91952
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91952
--- Comment #5 from Allison Karlitskaya
---
One could imagine (as a first step) that __default_value__() would be
implemented by way of a simple code transformation whenever it is encountered.
An additional block could be added and the variable
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91952
--- Comment #4 from Allison Karlitskaya
---
(In reply to Jakub Jelinek from comment #3)
> First of all, not all automatic vars live on stack, some live in registers.
Sure. The register could also be initialised to the same value, of course.
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91952
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91952
--- Comment #2 from Allison Karlitskaya
---
Consider this example in way of clarification:
void cleanup_func (void **ptr);
void *init (void);
void
function (bool condition)
{
if (condition)
goto out;
__attribute__((__cleanup__(cleanu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91952
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|