This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On 01/31/2017 03:59 PM, Joseph Myers wrote:
As I mentioned to Jakub, I see things differently, but I can certainly see both your and Jakub's point of view.On Tue, 31 Jan 2017, Jeff Law wrote:My general inclination is to ask this to wait for gcc-8 as it is not a regression, but instead a false positive in a new warning.I'd hope it would be possible for current releases of GCC and glibc to build with each other. As this seems to be a case where the warning is clearly bogus (and started appearing during GCC stage 4), a fix in GCC seems more appropriate than disabling the warning for that code in glibc.
The irony here is I'm currently poking at 79095 which is a false positive in a new warning as well and marked as a regression. One could make the same arguments on both sides about that BZ :-)
Given we've got two release managers view 79275 as a regression and one non-release-manager that does not, I won't push on the not-a-regression issue. I'll add the regression marker and put the patch back in the queue.
jeff
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |