This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug sanitizer/63958] [5 Regression] bootstrap failure in the sanitizer libs on sparc-linux-gnu
- From: "davem at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 19 Nov 2014 22:13:46 +0000
- Subject: [Bug sanitizer/63958] [5 Regression] bootstrap failure in the sanitizer libs on sparc-linux-gnu
- Auto-submitted: auto-generated
- References: <bug-63958-4 at http dot gcc dot gnu dot org/bugzilla/>
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 build failure that stood for 9 months in a release of gcc.
This current situation is completely unacceptable, and if you are going to get
into a commit war with me when I am simply trying to fix the build which you
both broke and refused to fix for 9+ months, that's extremely anti-social and
demonstrates how the current situation is not working and is bad for gcc
development overall.