Custom Query (245 matches)

Hi/2.

386/builtin.h includes stdint.h. This may not be a problem on C, however this may be a problem on C++. Because, stdint.h does not define some macros such as INT64_C() on C++ by default. It needs some macros such as __STDC_CONSTANT_MACROS are declared.

So if stdint.h is included once without macro declaration on C++, later macros such as INT64_C() are not declares even if stdint.h is included explicitly.

For example,

#include <vector>
#include <iostream>

#define __STDC_CONSTANT_MACROS
#include <stdint.h>

int main()
{
    std::cout << INT64_C(0) << "\n";

    return 0;
}

This fails.

vector.cpp: In function `int main()':
vector.cpp:9: error: `INT64_C' undeclared (first use this function)
vector.cpp:9: error: (Each undeclared identifier is reported only once for each 
   function it appears in.)

However, this succeeds on other platforms such as mingw-482.

Hi/2.

C++11 does not requires additinoal macros to define some constant/limit macros of stdint.h.

Involving paths registered in the kLIBC path rewriter causes a crash when doing mkstemp in the forked child (the test case attached). If I use open instead of mkstemp, then the program doesn't crash but instead creates a file in a wrong location.

In the test case I use paths starting with /tmp which is mapped to %TMP% (which is set to D:\Temp). In case of open the file is created in D:\ instead of D:\Temp. I also experience similar troubles with other rewriter paths.

Note that if execute the same mkstemp or open from the parent process, all works as it should.