Re: [Mingw-w64-public] [PATCH] Add some missing IMAGE_DLLCHARACTERISTICS_* constants

2015-06-01 Thread İsmail Dönmez
On Thu, May 28, 2015 at 8:58 PM, İsmail Dönmez ism...@donmez.ws wrote:
 On Thu, May 28, 2015 at 6:51 PM, Jacek Caban ja...@codeweavers.com wrote:
 On 05/28/15 17:29, İsmail Dönmez wrote:
 On Thu, May 28, 2015 at 4:49 PM, Jacek Caban ja...@codeweavers.com wrote:
 On 05/28/15 11:06, İsmail Dönmez wrote:
 On Mon, May 25, 2015 at 7:47 PM, İsmail Dönmez ism...@donmez.ws wrote:
 Hi,
  .
 Noticed while trying to compile the application from
 http://blogs.msdn.com/b/oldnewthing/archive/2015/05/18/10615339.aspx .

 Patch attached.
 ping?

 Looks good to me.
 Could you please apply it? Thanks!

 I committed the change, but I noticed that you modified winnt.h from
 widl directory. I removed that part because that's just an internal side
 effect of importing it from Wine. The one we care about is in
 mingw-w64-headers/include.

 Btw, without winnt.h change, I still cannot compile the example
 program from 
 http://blogs.msdn.com/b/oldnewthing/archive/2015/05/18/10615339.aspx
 so I think, it also should be applied.

Would you mind applying the winnt.h part too? I guess it wouldn't hurt
to keep those definitions in sync.

ismail

--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public


Re: [Mingw-w64-public] [PATCH] Add some missing IMAGE_DLLCHARACTERISTICS_* constants

2015-06-01 Thread İsmail Dönmez
Hi,

On Mon, Jun 1, 2015 at 12:25 PM, Jacek Caban ja...@codeweavers.com wrote:
 On 06/01/15 10:53, İsmail Dönmez wrote:
 On Thu, May 28, 2015 at 8:58 PM, İsmail Dönmez ism...@donmez.ws wrote:
 On Thu, May 28, 2015 at 6:51 PM, Jacek Caban ja...@codeweavers.com wrote:

 I committed the change, but I noticed that you modified winnt.h from
 widl directory. I removed that part because that's just an internal side
 effect of importing it from Wine. The one we care about is in
 mingw-w64-headers/include.
 Btw, without winnt.h change, I still cannot compile the example
 program from 
 http://blogs.msdn.com/b/oldnewthing/archive/2015/05/18/10615339.aspx
 so I think, it also should be applied.
 Would you mind applying the winnt.h part too? I guess it wouldn't hurt
 to keep those definitions in sync.

 As I said, winnt.h from widl directory is not meant to be used to build
 anything with mingw-w64 except internal widl usage. Please prepare and
 test a patch for mingw-w64-header/include/winnt.h.

Now I get it, please see the attached patch.
diff --git a/mingw-w64-headers/include/winnt.h b/mingw-w64-headers/include/winnt.h
index bfecb7b..8d8bd0d 100644
--- a/mingw-w64-headers/include/winnt.h
+++ b/mingw-w64-headers/include/winnt.h
@@ -5878,6 +5878,7 @@ __buildmemorybarrier()
 #define IMAGE_SUBSYSTEM_XBOX 14
 #define IMAGE_SUBSYSTEM_WINDOWS_BOOT_APPLICATION 16
 
+#define IMAGE_DLLCHARACTERISTICS_HIGH_ENTROPY_VA 0x0020
 #define IMAGE_DLLCHARACTERISTICS_DYNAMIC_BASE 0x0040
 #define IMAGE_DLLCHARACTERISTICS_FORCE_INTEGRITY 0x0080
 #define IMAGE_DLLCHARACTERISTICS_NX_COMPAT 0x0100
@@ -5886,6 +5887,7 @@ __buildmemorybarrier()
 #define IMAGE_DLLCHARACTERISTICS_NO_BIND 0x0800
 #define IMAGE_DLLCHARACTERISTICS_APPCONTAINER 0x1000
 #define IMAGE_DLLCHARACTERISTICS_WDM_DRIVER 0x2000
+#define IMAGE_DLLCHARACTERISTICS_GUARD_CF 0x4000
 #define IMAGE_DLLCHARACTERISTICS_TERMINAL_SERVER_AWARE 0x8000
 
 #define IMAGE_DIRECTORY_ENTRY_EXPORT 0
--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public


Re: [Mingw-w64-public] [PATCH] Add some missing IMAGE_DLLCHARACTERISTICS_* constants

2015-06-01 Thread Jacek Caban
On 06/01/15 10:53, İsmail Dönmez wrote:
 On Thu, May 28, 2015 at 8:58 PM, İsmail Dönmez ism...@donmez.ws wrote:
 On Thu, May 28, 2015 at 6:51 PM, Jacek Caban ja...@codeweavers.com wrote:

 I committed the change, but I noticed that you modified winnt.h from
 widl directory. I removed that part because that's just an internal side
 effect of importing it from Wine. The one we care about is in
 mingw-w64-headers/include.
 Btw, without winnt.h change, I still cannot compile the example
 program from 
 http://blogs.msdn.com/b/oldnewthing/archive/2015/05/18/10615339.aspx
 so I think, it also should be applied.
 Would you mind applying the winnt.h part too? I guess it wouldn't hurt
 to keep those definitions in sync.

As I said, winnt.h from widl directory is not meant to be used to build
anything with mingw-w64 except internal widl usage. Please prepare and
test a patch for mingw-w64-header/include/winnt.h.

Thanks,
Jacek

--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public


Re: [Mingw-w64-public] Set a larger pch file size limit? was : can anyone supply a debug version of cc1plus.exe?

2015-06-01 Thread asmwarrior
On 2015-5-31 16:22, asmwarrior wrote:
 On 2015-5-23 9:39, asmwarrior wrote:
 I just want to hunt the GCC bug: (big pch file will crash cc1plus.exe)
 56926 – Crash (without ICE) while compiling Boost.Math - 
 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56926

 It turns out that build the GCC and G++ myself is too complex for me, so I 
 would like to see if someone can supply a debug version of tool chain, so 
 that I can run them under gdb to see where it crashed.

 BTW: I see that the latest LD can have separate debug file generated, so 
 maybe, we can use it.

 Thanks.

 Hi, with Kai's suggestion: https://sourceforge.net/p/mingw-w64/bugs/382/
 I guess that the hard limit value is 128M, and I would suggest a larger value 
 for this variable. See here:
 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56926#c16
 Any one would like to try a new build of gcc?
 
 There are some similar related discussion, see:
 1, mingw - cc1plus.exe crash when using large precompiled header file
 http://stackoverflow.com/questions/10841306/cc1plus-exe-crash-when-using-large-precompiled-header-file
 2, MinGW-w64 - for 32 and 64 bit Windows / Mailing Lists 
 https://sourceforge.net/p/mingw-w64/mailman/message/30846624/
 
 Thanks.
 

Hi, good news, since I don't see any one rebuild a gcc chain by a larger 
pch_VA_max_size value recently.
Today, I do it myself by modify the cc1plus.exe in a binary editor, just 
changed the values in the three referenced instructions.
I changed the value from 128M to 512M.
See details here:
Comment 17 - https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56926#c17
Now, the modified cc1plus.exe never crash with a 200M pch file.
So, the crash issue can to solved now!!!

asmwarrior


--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public