From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 2510B385B83F; Fri, 1 Dec 2023 10:17:39 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2510B385B83F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1701425859; bh=39RuOBk74UTGbJS10lFzEurFTVmNYorWcSZ5bEEzXuM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=SfAo5AbvezdOfXqE4dDUTXoCCv3A4bA1f+dA2zOEVjzGve3i999XJqoCWyMsung1f yxiyS37dPTKH9ahY7LQ8VUFFbo8DksMZR14smDizPU6ygntkERUMbjLhkVHbj+46St pPaHfcz4v57npCFQBYSV2f/bl1kVeNA493/rCPnE= From: "fw at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcc/109289] Conflicting types for built-in functions in libgcc/emutls.c Date: Fri, 01 Dec 2023 10:17:36 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libgcc X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: normal X-Bugzilla-Who: fw at gcc dot gnu.org X-Bugzilla-Status: NEW 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: 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=3D109289 --- Comment #3 from Florian Weimer --- Jan, do you actually experience a build failure? The part you quoted only s= hows warnings. Thomas, the safe thing to do would be to use __builtin_calloc and __builtin_realloc in those spots because it avoids a dependency on an exter= nal header that might not exist at this point.=