Re: Re: Re: GCC 6.1 Hard-coded C++ header paths and relocation problem on Windows

2016-05-09 Thread lh mouse
We use neither --with-sysroot nor --with-build-sysroot. The reason is that, the hard-coded path in GCC repository - that is, the /mingw/ one - does not actually exist. In order to build GCC for mingw targets, we take either solution: 0) Make a symlink (or rather, a copy, since Windows does not su

Re: Re: Re: GCC 6.1 Hard-coded C++ header paths and relocation problem on Windows

2016-05-09 Thread lh mouse
I have a vision. It is gcc/gcc/incpath.c that the problem is in. I had been looking through that file for a few days but eventually gave up. It is worth mentioning that adding an '-iprefix /this/need/not/exist' vanishes the problem. This might have something to do with the following line in incpa

Re: GNU C: Implicit int and implicit function definitions

2016-05-20 Thread lh mouse
Implicit function declarations result in warnings since C99 or GNU99 and '-pedantic-errors' turns them into errors. The same goes for implicit return types. -- Best regards, lh_mouse 2016-05-20 --

Contribute to GCC - the MCF thread model for MinGW targets

2016-06-11 Thread lh mouse
Hello GCC developers, I have implemented a gthread library for both the i686 and x86_64 MinGW targets, which supports all c++0x thread features required by . This library is experimental and stil lrequires testing. However Kai suggested I donate it to the FSF so it could be merged into the GCC u

Re: RE: [Mingw-w64-public] Contribute to GCC - the MCF thread model for MinGWtargets

2016-06-12 Thread lh mouse
efficient and c++0x conforming thread implementation for GCC on MinGW targets. -- Best regards, lh_mouse 2016-06-12 --------- 发件人:Ruben Van Boxem 发送日期:2016-06-12 15:48 收件人:lh mouse,gcc,mingw-w64-public 抄送: 主题:RE: [Mi

Potential bug about the order of destructors of static objects and atexit() callbacks in C++?

2016-08-01 Thread lh mouse
Hello GCC developers, Reading the ISO C++ standard, > 3.6.4 Termination [basic.start.term] > 3 If the completion of the initialization of an object with > static storage duration is sequenced before a call to std::atexit > (see , 18.5), the call to the function passed to std::atexit > is sequenced