Re: [Mingw-w64-public] Erroneous "out of memory" using LTO

2017-03-14 Thread Riot
Thanks for the detailed response Ruben, I appreciate it. We do use gold on Linux and perhaps that's the reason we don't encounter these sorts of issues, although we're building with 64bit tools there in any case, so perhaps we would only see them in a purely 32bit build environment. We've looked

Re: [Mingw-w64-public] Erroneous "out of memory" using LTO

2017-03-14 Thread Ruben Van Boxem
Additionally, if you look at the default values of the parameters you're changing, it seems you're stretching the (compiler) implementation quite a bit, so I'm not sure why you are surprised that the compiler can't handle it. It seems like you're loading ten blocks of granite into a minivan and sur

Re: [Mingw-w64-public] Erroneous "out of memory" using LTO

2017-03-14 Thread Ruben Van Boxem
The default values can be found in https://github.com/gcc-mirror/gcc/blob/master/gcc/params.def For example, but I guess you already knew where to find those. Op 14 mrt. 2017 11:55 p.m. schreef "Ruben Van Boxem" < vanboxem.ru...@gmail.com>: > Additionally, if you look at the default values of th

Re: [Mingw-w64-public] Erroneous "out of memory" using LTO

2017-03-14 Thread Ruben Van Boxem
Hello again, Op 14 mrt. 2017 9:26 p.m. schreef "Riot" : On 14 March 2017 at 18:53, Ruben Van Boxem wrote: > These options look quite... inefficient... and frankly suboptimal. I hope > you do regular benchmarking to see if these are actually any/much better > than default -O2 -march=native 'or w

Re: [Mingw-w64-public] Erroneous "out of memory" using LTO

2017-03-14 Thread Riot
On 14 March 2017 at 18:53, Ruben Van Boxem wrote: > These options look quite... inefficient... and frankly suboptimal. I hope > you do regular benchmarking to see if these are actually any/much better > than default -O2 -march=native 'or whatever). Yes, we benchmark extensively, and we would not

Re: [Mingw-w64-public] Erroneous "out of memory" using LTO

2017-03-14 Thread Ruben Van Boxem
2017-03-13 17:27 GMT+01:00 Riot : > Thanks for the quick replies. > > I have realised now I made a mistake in my original listing, and omitted > some commandline options that had been included by our build script, and > disabling one of these prevents the problem occurring. > > The linker options

Re: [Mingw-w64-public] LoadImage defined in x86_64-w64-mingw32/include/winuser.h

2017-03-14 Thread David Grayson
You can run "grep -ir LoadImage" to figure out what kind of definition for LoadImage is provided by mingw-w64. It looks like include/winuser.h has this line: #define LoadImage __MINGW_NAME_AW(LoadImage) So in your header file for your LoadImage class, you can simply write: #undef LoadImage

Re: [Mingw-w64-public] Fwd: Fix for winreg.h

2017-03-14 Thread Liu Hao
On 2017/3/14 18:57, JonY wrote: > Looks like LH has already applied this to master. Yes I pushed it a couple of days ago. He said his mails were suspended on this ML (and it seemed so). Best regards, LH_Mouse -- Check o

Re: [Mingw-w64-public] Fwd: Fix for winreg.h

2017-03-14 Thread JonY
On 03/08/2017 08:39 AM, MichaƂ Janiszewski wrote: > Hi, > I would like to contribute a minor patch (attached) to fix > RegSetKeyValueW declaration in winreg.h. > I'm not familiar with the process of submitting patches, so please let > me know if I need to do something else as well. > It's the third

[Mingw-w64-public] LoadImage defined in x86_64-w64-mingw32/include/winuser.h

2017-03-14 Thread Mario Emmenlauer
I'm not sure where to ask about this, please redirect me as needed! I have a C++ class with a function "LoadImage", which caused a compile error on Windows. After some digging, I think that a define or function from winuser.h with a similar name is the culprit. I'm slightly confused by this, beca