Def not a GCC issue. Here's what I built on CYGWIN using both MinGW and CYGWIN
(aka "native") toolchains.
$ cat trig.c
#include
#include
#include
int main( int argc, char *argv[] ) {
double s1 = sin(strtod(argv[1], NULL));
double s2 = sin(3.1415926535897931);
printf("gcc version: %d.%d.%
Hi,
The demo:
##
/* trig.c */
#define __USE_MINGW_ANSI_STDIO 1
#include
#include
#include
int main( int argc, char *argv[] ) {
double s1 = sin(strtod(argv[1], NULL));
double s2 = sin(3.1415926535897931);
printf("gcc version: %d.%d.%d\n", __GNUC__, __GNUC_MINOR__,
__GNUC_PATCH
> Why do you ever want to call `_setjmpex()` directly? It is only used to
> implement the standard
> `setjmp()` macro, which in the case of UCRT calls `__intrinsic_setjmpex()`.
Same question as mine. Need it here
https://github.com/Perl/perl5/blob/blead/dist/threads/threads.xs
_
在 2021-06-06 14:05, Biswapriyo Nath 写道:
* Source: int main() { _setjmpex(0,0); }
* Compiler command: gcc test.c
* msvcrt ok.
* ucrt linking error
Why do you ever want to call `_setjmpex()` directly? It is only used to implement the standard
`setjmp()` macro, which in the case of UCRT calls `
On Mon, 7 Jun 2021, Liu Hao wrote:
在 2021-06-05 14:16, Martin Storsjö 写道:
The second implementation, which was under the 'strtold' name, was
lacking (it didn't support e.g. strings like "0x125p-1"), while the
'__mingw_strtold' one seemed correct and complete.
Signed-off-by: Martin Storsjö
---
