https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63958
--- Comment #15 from chefmax at gcc dot gnu.org ---
Author: chefmax
Date: Tue Nov 8 22:06:02 2016
New Revision: 241978
URL: https://gcc.gnu.org/viewcvs?rev=241978=gcc=rev
Log:
PR sanitizer/63958
Reapply:
2014-10-14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63958
--- Comment #14 from Maxim Ostapenko ---
Author: chefmax
Date: Wed Oct 21 07:44:35 2015
New Revision: 229113
URL: https://gcc.gnu.org/viewcvs?rev=229113=gcc=rev
Log:
libsanitizer/
PR sanitizer/63958
Reapply:
2014-10-14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63958
--- Comment #11 from Jakub Jelinek jakub at gcc dot gnu.org ---
Author: jakub
Date: Mon Mar 9 18:25:28 2015
New Revision: 221283
URL: https://gcc.gnu.org/viewcvs?rev=221283root=gccview=rev
Log:
PR sanitizer/63958
Reapply:
2014-10-14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63958
Jakub Jelinek jakub at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63958
--- Comment #12 from Jakub Jelinek jakub at gcc dot gnu.org ---
Fixed for GCC 5 now, but the problem will likely reappear during next merge :(.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63958
Matthias Klose doko at gcc dot gnu.org changed:
What|Removed |Added
Status|WAITING |NEW
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63958
Jakub Jelinek jakub at gcc dot gnu.org changed:
What|Removed |Added
CC||doko at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63958
--- Comment #8 from Jakub Jelinek jakub at gcc dot gnu.org ---
The r216224 change apparently applies cleanly to the current sources, does it
fix all the sparc*-linux build issues? My SPARC box is long time dead...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63958
Richard Biener rguenth at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63958
Richard Biener rguenth at gcc dot gnu.org changed:
What|Removed |Added
Version|unknown |5.0
Target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63958
--- Comment #1 from Kostya Serebryany kcc at gcc dot gnu.org ---
Please send patches upstream:
https://code.google.com/p/address-sanitizer/wiki/HowToContribute
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63958
davem at gcc dot gnu.org changed:
What|Removed |Added
CC||davem at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63958
--- Comment #3 from Kostya Serebryany kcc at gcc dot gnu.org ---
I am very sorry that you are so upset, but the workflow will not change.
All changes to sanitizer files (except for GCC-specific tests and make files)
have to go to upstream first.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63958
--- Comment #4 from davem at gcc dot gnu.org ---
You cannot have it both ways.
If you demand people go through upstream, you have to be responsive to fixing
build failures yourselves. Because it is the sanitizer developers who
introduced this
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63958
H.J. Lu hjl.tools at gmail dot com changed:
What|Removed |Added
CC||hjl.tools at gmail
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63958
--- Comment #6 from Kostya Serebryany kcc at gcc dot gnu.org ---
I am not at war with anyone and if I am, I give up and surrender.
But whoever wants the sanitizers to work on SPARC [s]he will have to work with
us upstream. We can not fix build
16 matches
Mail list logo
