https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56682
Sam James changed:
What|Removed |Added
Target Milestone|--- |15.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56682
sandra at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCO
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56682
--- Comment #6 from GCC Commits ---
The master branch has been updated by Sandra Loosemore :
https://gcc.gnu.org/g:313edeeeb607fe32da5633cfb6f91977add446f6
commit r15-7899-g313edeeeb607fe32da5633cfb6f91977add446f6
Author: Sandra Loosemore
Date
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56682
--- Comment #5 from Jakub Jelinek ---
Maybe for leak, not sure about that. For UBSan I think it isn't needed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56682
--- Comment #4 from sandra at gcc dot gnu.org ---
Is -g also recommended for the other -fsanitize= options?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56682
--- Comment #3 from Martin Liška ---
I really believe there's no need for any extra options on top of
-sanitize={address,thread} right now.
The only recommendation would be about the -g option in order to have nice
backtraces and variable locati
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56682
sandra at gcc dot gnu.org changed:
What|Removed |Added
CC||dodji at gcc dot gnu.org,
