Re: [Mingw-w64-public] MINGW trademark claims

7;t be confused by trolls, ppa. Roland Schwingel --------- Roland Schwingel, Head of Research & Development OneVision Software AG, Dr. Leo-Ritter-Str. 9, 93049 Regensburg, Germany Phone: +49 941 78004 0

Re: [Mingw-w64-public] MINGW trademark claims

fused by trolls, ppa. Roland Schwingel --------- Roland Schwingel, Head of Research & Development OneVision Software AG, Dr. Leo-Ritter-Str. 9, 93049 Regensburg, Germany Phone: +49 941 78004 0 --- Fax

Re: [Mingw-w64-public] [Poll] Move to git

Hi... As someone, who finds SVN more straight forward... [ ] Yes, move to git [X] No, continue with SVN Roland -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hinder

Re: [Mingw-w64-public] Trouble with pow()

Hi... Whenever possible I investigated pow() more the last days. I calculated billions of pow() values on windows/linux/mac and compared them. First one my main test code. I did let it run in variety of numeric ranges. // powtest2.c // gcc -O3 -fno-builtin powtest2.c -o powtest (-lm) #include #

Re: [Mingw-w64-public] Trouble with pow()

Hi Kai ... It's me again... :-) Kai Tietz wrote on 24.03.2014 17:41:33: [...] > Sorry, I can't confirm this issue. > > Anyway thanks for the test. I might add it to our testcases. > I tried it with current toolchain built, and for me this test passes > without flaws. > I assume that you might

Re: [Mingw-w64-public] Trouble with pow()

Hi Kai... Kai Tietz wrote on 24.03.2014 15:19:03: > Hi Roland, > > could you please provide a small testcase > demonstrating this end-less loop? Testcase is quite simple: #include #include int main(int argc,const char **argv) { printf("before\n"); pow(2,-2147483648.);

[Mingw-w64-public] Trouble with pow()

Hi... Recently a problem was discovered with the function pow(). It is possible to let it's computation run into an infinite loop, when using mingw-w64-crt! I took a *DEEP* look into it: This - fortunately - only happens with a special case: x^-2147483648 This is (in hexadecimal) 0x8000.

Re: [Mingw-w64-public] ntsecapi.h: Incomplete definition of SECURITY_LOGON_SESSION_DATA

Hi Kai.. Thanks... Applied as r6420. Greetings from OneVision, Roland Kai Tietz wrote on 13.12.2013 09:58:58: > Hellor Roland, > > patch is ok. Please apply. > > Regards, > Kai > > 2013/12/12 Roland Schwingel : > > Hi... > > > >

[Mingw-w64-public] ntsecapi.h: Incomplete definition of SECURITY_LOGON_SESSION_DATA

Hi... Today I discovered that the definition of SECURITY_LOGON_SESSION_DATA in ntsecapi.h is incomplete. It is missing several fields. Reference: http://msdn.microsoft.com/en-us/library/aa380128.aspx Also the substruct LSA_LAST_INTER_LOGON_INFO is missing. Reference: http://msdn.microsoft.co

Re: [Mingw-w64-public] tcl fails to build due to conflicting implementation of EXCEPTION_REGISTRATION structure

Hi... Erik van Pienbroek wrote on 17.09.2013 22:40:14: > Erik van Pienbroek schreef op di 17-09-2013 om 20:34 [+0200]: > > The test mass rebuild has shown that > > there are only 2 build failures remaining: tk and tcl which both suffer > > from the issue mentioned in this thread. > > The pa

[Mingw-w64-public] setjmp/longjmp blues

Hi... Presently I am migrating a big codebase from GCC 4.4.3 to 4.8.2 using the current trunk mingw-w64 crt and headers. I am using a self built toolchain with SEH for 64bit windows and sjlj on 32bit windows. Everything appears to be fine when compiling for 32bit. But I am/was facing some trou

[Mingw-w64-public] [PATCH] Fix stray BOOL struct member breaking ObjectiveC

Hi ... Mingw-w64 headers do use WINBOOL instead of BOOL as boolean data type to not conflict with ObjectiveC (GNUStep) BOOL definition. Unfortunately one BOOL slipped in breaking building of GNUStep with current headers. The attached patch fixes this. Roland Changelog: 2013-03-01 Roland