在 2022/10/11 05:20, Martin Storsjö 写道:
On Mon, 10 Oct 2022, Pali Rohár wrote:
Anyway, why exported functions are defined via _CRTIMP? Should not be
also be defined via __MINGW_IMP_SYMBOL/dllimport to avoid generating
unnecessary thunk/wrapper for mingw-w64 runtime code?
I think it's a matter
On Mon, 10 Oct 2022, Pali Rohár wrote:
On Monday 10 October 2022 14:25:07 Martin Storsjö wrote:
But when building code within mingw-w64-crt, _CRTIMP expands to nothing. I
guess this is generally desireable when implementing some of the functions
that are marked _CRTIMP (we generally shouldn't
On Monday 10 October 2022 14:25:07 Martin Storsjö wrote:
> Historically, the _CRTIMP macro comes from how it is used in upstream
> msvcrt; you can link the CRT either statically or dynamically. If intending
> to link statically, _CRTIMP expands to nothing, while if intending to link
> dyanmically,
在 2022-10-04 20:56, Martin Storsjö 写道:
Signed-off-by: Martin Storsjö
---
mingw-w64-headers/include/winnt.h | 16
1 file changed, 16 insertions(+)
LGTM. Thanks.
--
Best regards,
LIU Hao
OpenPGP_signature
Description: OpenPGP digital signature
__
在 2022/10/10 19:25, Martin Storsjö 写道:
I think this example kinda misses the point; here you already do have an __imp__tzset elsewhere
(from the import library) - but we only do manually define e.g. __imp__tzset when we're in a
configuration where the import library doesn't provide it (or we'v
On Sun, 9 Oct 2022, LIU Hao wrote:
在 2022/10/9 18:05, Pali Rohár 写道:
Ok, I see.
Anyway, I quite do not understand why some crt exported functions are
marked with _CRTIMP (as it is empty during CRT build) and some exported
variables use __MINGW_IMP_SYMBOL. I would expect that all exported
func
