https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67198
--- Comment #4 from boger at us dot ibm.com --- I'll admit I'm not familiar with how this field could ever be used. But you are saying that no code will ever try to do a compare with this field when has a value greater than 127? If it did then it would get the wrong result because of the sign. In my opinion it is better to fix it now instead of wait until someone potentially hits a problem with it, when it will cost a lot more to investigate and fix. Especially since go 1.5 in golang is correct. Yesterday I got another (unrelated) question about the granularity of gccgo build tags. Seems like a more precise gccgo build tag would help here.
