This is the mail archive of the gcc-help@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]

Implement weak divmoddi4() and udivmoddi4() for internal use by the CRT and winpthreads?

From: Liu Hao <lh_mouse at 126 dot com>
To: mingw-w64-public at lists dot sourceforge dot net
Cc: "gcc-help at gcc dot gnu dot org" <gcc-help at gcc dot gnu dot org>
Date: Mon, 8 May 2017 12:41:58 +0800
Subject: Implement weak __divmoddi4() and __udivmoddi4() for internal use by the CRT and winpthreads?
Authentication-results: sourceware.org; auth=none

Hello all,

Since GCC 7, a new function `__divmoddi4()` is added in libgcc. When GCCperforms division of two 64-bit integers on i686, a call to thisfunction is emitted, which could result in undefined references to thisfunction when we are building part of the CRT (winpthreads for example,but I am not totally sure that our CRT is free of such issues). Isuggest we implement weak versions of these functions that are used onlyby the CRT (strong ones from libgcc are used if whenever available).


Source attached. Any ideas on this?

--
Best regards,
LH_Mouse

Attachment: divmod.c
Description: Text document

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Implement weak __divmoddi4() and __udivmoddi4() for internal use by the CRT and winpthreads?

Implement weak divmoddi4() and udivmoddi4() for internal use by the CRT and winpthreads?