Re: [Mingw-w64-public] SEH

On Mon, Aug 6, 2012 at 11:22 AM, Ruben Van Boxem wrote: > Op 6 aug. 2012 23:20 schreef "JonY" het > volgende: >> > What libgcc was built? dw2 or sjlj (or something else)? >> 64bit libgcc_s_seh-1.dll, 32bit libgcc_s_sjlj-1.dll. > Looking good then :-) Yeah, this is actually a really awesome thing

Re: [Mingw-w64-public] apparent "hang" using the experimental pthread library

Hi Kai, On 8/6/2012 4:58 PM, Kai Tietz wrote: > I have attached a modified version of winpthread (uncomress it and > rename it back to .dll). It would be great if you could test this > variant on your box, too. Thanks a lot for the modified libwinpthread-1.dll, and the continued help. I copied

Re: [Mingw-w64-public] SEH

Op 6 aug. 2012 23:20 schreef "JonY" het volgende: > > On 8/7/2012 05:01, Ruben Van Boxem wrote: > > Op 6 aug. 2012 22:59 schreef "JonY" het > > volgende: > >> > >> On 8/7/2012 02:01, niXman wrote: > >>> 2012/8/6 JonY: > Actually, I just succeeded in getting around that error, > x86_64-w

Re: [Mingw-w64-public] SEH

On 8/7/2012 05:03, niXman wrote: > 2012/8/7 JonY: > >> You can leave the --enable-sjlj-exceptions for the 32bit case for now, >> since it can't do SEH anyway. > > libgcc/unwind-c.c: In function '__gcc_personality_seh0': > libgcc/unwind-c.c:242:14: error: '__gcc_personality_imp' undeclared > >

Re: [Mingw-w64-public] SEH

On 8/7/2012 05:01, Ruben Van Boxem wrote: > Op 6 aug. 2012 22:59 schreef "JonY" het > volgende: >> >> On 8/7/2012 02:01, niXman wrote: >>> 2012/8/6 JonY: Actually, I just succeeded in getting around that error, x86_64-w64-mingw32-gcc 4.8.0 is working fine here. Remove the --ena

Re: [Mingw-w64-public] SEH

2012/8/7 JonY: > You can leave the --enable-sjlj-exceptions for the 32bit case for now, > since it can't do SEH anyway. libgcc/unwind-c.c: In function '__gcc_personality_seh0': libgcc/unwind-c.c:242:14: error: '__gcc_personality_imp' undeclared -- Regards, niXman __

Re: [Mingw-w64-public] SEH

Op 6 aug. 2012 22:59 schreef "JonY" het volgende: > > On 8/7/2012 02:01, niXman wrote: > > 2012/8/6 JonY: > >> Actually, I just succeeded in getting around that error, > >> x86_64-w64-mingw32-gcc 4.8.0 is working fine here. > >> > >> Remove the --enable-sjlj-exceptions part from your configure, do

Re: [Mingw-w64-public] SEH

On 8/7/2012 02:01, niXman wrote: > 2012/8/6 JonY: >> Actually, I just succeeded in getting around that error, >> x86_64-w64-mingw32-gcc 4.8.0 is working fine here. >> >> Remove the --enable-sjlj-exceptions part from your configure, don't >> disable it either. --enable-sjlj-exceptions still makes wi

Re: [Mingw-w64-public] apparent "hang" using the experimental pthread library

On 8/6/2012 3:56 PM, Kai Tietz wrote: > 2012/8/6 Kyle : >> On 8/6/2012 1:59 PM, Kai Tietz wrote: >>> 2012/8/6 Kyle : On 8/4/2012 3:38 AM, Kai Tietz wrote: > 2012/8/4 Kyle Schwarz : >> On 7/27/2012 5:37 PM, Kai Tietz wrote: I have tried it, thanks for the patch! >>

Re: [Mingw-w64-public] apparent "hang" using the experimental pthread library

2012/8/6 Kyle : > On 8/6/2012 1:59 PM, Kai Tietz wrote: >> 2012/8/6 Kyle : >>> On 8/4/2012 3:38 AM, Kai Tietz wrote: 2012/8/4 Kyle Schwarz : > On 7/27/2012 5:37 PM, Kai Tietz wrote: >>> I have tried it, thanks for the patch! >>> >>> Unfortunately it appears that (ffmpeg + libx2

Re: [Mingw-w64-public] apparent "hang" using the experimental pthread library

On 8/6/2012 1:59 PM, Kai Tietz wrote: > 2012/8/6 Kyle : >> On 8/4/2012 3:38 AM, Kai Tietz wrote: >>> 2012/8/4 Kyle Schwarz : On 7/27/2012 5:37 PM, Kai Tietz wrote: >> I have tried it, thanks for the patch! >> >> Unfortunately it appears that (ffmpeg + libx264 using it at least) >>>

[Mingw-w64-public] GCC 4.6.3-1-release and Clang 3.1 release by rubenvb

Hi everyone, I have finished messing up my scripts and fixing them afterwards. I bring you another GCC 4.6.3 build, with MinGW-w64 v2.0.5. Changes since the last build: - optimization options are for sure -O2 -march=nocona -mtune=core2. This means SSE3 is required. - I now build 32-bit to 64-bi

Re: [Mingw-w64-public] apparent "hang" using the experimental pthread library

2012/8/6 Kyle : > On 8/6/2012 2:45 PM, Kai Tietz wrote: >> Another question I have. Which ff-tool is blocking for you? I tried >> ffplay, which didn't dead-locked on my Windows-box (i7 Windows 7 >> 64-bit). Could you provide me with example film/stream, so that I am >> able to reproduce your dea

[Mingw-w64-public] Question: improved win32 threading model for Vista+

Hello, A few months ago there was a conversation on this list about an improved threading model that will avoid the dependency on pthread-like wrappers. Sometimes it was referenced as win64, which a few developers considered it wrong and that "win32" threading should be enhanced instead. Either

Re: [Mingw-w64-public] Problem with __int128 and Clang

2012/4/10 Ozkan Sezer : > I pushed r4950 for __int128 and clang. Please correct further if necessary. This is a change that would be nice to have in the v2.x branch. I'll be releasing Clang 3.1 release builds (which work great for 32-bit), and for now (v2.0.5) I'll have to modify the header mysel

Re: [Mingw-w64-public] apparent "hang" using the experimental pthread library

On 8/6/2012 2:45 PM, Kai Tietz wrote: > Another question I have. Which ff-tool is blocking for you? I tried > ffplay, which didn't dead-locked on my Windows-box (i7 Windows 7 > 64-bit). Could you provide me with example film/stream, so that I am > able to reproduce your dead-lock? Using ffmpeg.

Re: [Mingw-w64-public] apparent "hang" using the experimental pthread library

Another question I have. Which ff-tool is blocking for you? I tried ffplay, which didn't dead-locked on my Windows-box (i7 Windows 7 64-bit). Could you provide me with example film/stream, so that I am able to reproduce your dead-lock? Thanks in advance, Kai ---

Re: [Mingw-w64-public] SEH

2012/8/6 JonY: > Actually, I just succeeded in getting around that error, > x86_64-w64-mingw32-gcc 4.8.0 is working fine here. > > Remove the --enable-sjlj-exceptions part from your configure, don't > disable it either. --enable-sjlj-exceptions still makes win64 target use > sjlj, though there is a

Re: [Mingw-w64-public] apparent "hang" using the experimental pthread library

2012/8/6 Kyle : > On 8/4/2012 3:38 AM, Kai Tietz wrote: >> 2012/8/4 Kyle Schwarz : >>> On 7/27/2012 5:37 PM, Kai Tietz wrote: > I have tried it, thanks for the patch! > > Unfortunately it appears that (ffmpeg + libx264 using it at least) > appears to deadlock (?) after a few seconds

Re: [Mingw-w64-public] apparent "hang" using the experimental pthread library

On 8/4/2012 3:38 AM, Kai Tietz wrote: > 2012/8/4 Kyle Schwarz : >> On 7/27/2012 5:37 PM, Kai Tietz wrote: I have tried it, thanks for the patch! Unfortunately it appears that (ffmpeg + libx264 using it at least) appears to deadlock (?) after a few seconds. Here's an ex

Re: [Mingw-w64-public] [patch/bulk] Introduce __LONG32, part 42

On Aug 6 18:08, Kai Tietz wrote: > Great. The patch for strsafe.h is ok. > > Thanks for all this hard work, > Kai Sure. There may be some more cleanup required, but the bulk of the work should be done now. Thanks for your quick reviews, Corinna --

Re: [Mingw-w64-public] [patch/bulk] Introduce __LONG32, part 42

Great. The patch for strsafe.h is ok. Thanks for all this hard work, Kai -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT mana

Re: [Mingw-w64-public] [patch/bulk] Introduce __LONG32, part 42

On Aug 6 17:49, Kai Tietz wrote: > Hi Corinna, > > patch 42 is ok. > > Thanks, > Kai > > PS: I think we are nearly through, aren't we? Almost. I just missed the patch to strsafe.h. See below. Corinna * strsafe.h: Change long to __LONG32 where appropriate. Index: strsafe.h =

Re: [Mingw-w64-public] [patch/bulk] Introduce __LONG32, part 42

Hi Corinna, patch 42 is ok. Thanks, Kai PS: I think we are nearly through, aren't we? -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed a

Re: [Mingw-w64-public] [patch/bulk] Introduce __LONG32, part 19

Hello Corinna, patch is ok. Thanks, Kai -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions wi

[Mingw-w64-public] [patch/bulk] Introduce __LONG32, part 42

Hi, Part 42 Thanks, Corinna * winsock.h: Change long to __LONG32 where appropriate. * winsock2.h: Ditto. * winuser.h: Ditto. * wmiatlprov.h: Ditto. * wmiutils.h: Ditto. * ws2spi.h: Ditto. * xa.h: Ditto. * xcmc.h: Ditto. *

Re: [Mingw-w64-public] [patch/bulk] Introduce __LONG32, part 18

Hello Corinna, patch is ok. Thanks, Kai -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions wi

Re: [Mingw-w64-public] [patch/bulk] Introduce __LONG32, part 17 1/2

Hello Corinna, Patch is ok. Please apply. Thanks, Kai -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. D

Re: [Mingw-w64-public] [patch/bulk] Introduce __LONG32, part 16

Hi Corinna, this patch is ok. Thanks, Kai -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions

Re: [Mingw-w64-public] [patch/bulk] Introduce __LONG32, part 17 3/4

Hi, :) Ok. Thanks, Kai -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoi

Re: [Mingw-w64-public] [patch/bulk] Introduce __LONG32, part 17

Hi, patch is ok. Thanks, Kai -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include

Re: [Mingw-w64-public] [patch/bulk] Introduce __LONG32, part 15

Patch is ok. Please apply. Thanks, Kai -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will

Re: [Mingw-w64-public] [patch/bulk] Introduce __LONG32, part 14

Hi Corinna, part 14 is ok. Thanks, Kai -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions wil

Re: [Mingw-w64-public] [patch/bulk] Introduce __LONG32, part 12b

Corinna, the patch is ok. 12b? You got tired by simple increasing patch-numbers? ;) Thanks, Kai -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape ha

Re: [Mingw-w64-public] [patch/bulk] Introduce __LONG32, part 12

Patch is ok. Thanks, Kai -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpo

Re: [Mingw-w64-public] [patch/bulk] Introduce __LONG32, part 10

Hi, this patch is fine. Please go ahead. Thanks, Kai -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. D

Re: [Mingw-w64-public] [patch/bulk] Introduce __LONG32, part 11

Hi Corinna, so this patch is ok, too. Thanks, Kai -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discu

Re: [Mingw-w64-public] [patch/bulk] Introduce __LONG32, part 9

Corinna, patch is ok for apply. Thanks, Kai -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions

[Mingw-w64-public] libgcj on i686-w64-mingw32

Hi everyone, NightStrike asked me on IRC if I also built libgcj, and I tried, but got this known error: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50895 So I will not be building it cause I can't :) Ruben -- Live Secur