From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id DC134385840D; Sat, 5 Nov 2022 12:53:04 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DC134385840D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1667652784; bh=Fb2YzZJUGrc2M4gkCfV9eTPX539sWpX3aKc31WwlNp0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=py4+EPAMt5k3Cw9E7JzI32sJjTDiIhAzpPS7OhbejANcyJty3zCh85+ZyE+yIwN6z Vb7hHvbYBSADOxtNgjo3ypVpgKbdd8jWptwCLTOg/r+rjDk+vkTrCpfXSAxSn9QrRL Pw577kYFZkCxxMrzDGzrJz9cc0lGDLKCklIdqNnc= From: "helmut at subdivi dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/80677] LIMITS_H_TEST is wrong Date: Sat, 05 Nov 2022 12:53:03 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: bootstrap X-Bugzilla-Version: 7.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: helmut at subdivi dot de X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D80677 Helmut Grohne changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |helmut at subdivi dot de --- Comment #3 from Helmut Grohne --- Created attachment 53832 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D53832&action=3Dedit eliminate the need for LIMITS_H_TEST entirely Rather than fix LIMITS_H_TEST, I now propose deleting it. The check that we= try to perform at build time with wrong paths can be deferred to runtime and th= en operated with correct paths. I'm using this patch since at least gcc-11 and only encountered one regression thus far. It triggers https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D80755 on hurd, but this is a= plain gcc bug that needs fixing anyway, so this should be good to go.=