Re: [Mingw-w64-public] [Patch] Issues with vsscanf - first draft

2016-07-07 Thread dw
On 7/7/2016 4:49 PM, Ozkan Sezer wrote: > On 7/8/16, dw wrote: >> In any case, did you have a chance to look at the patch? > Unfortunately no. Kai would be the guy for reviewing asm stuff. Ok then. I hope he has the time. How about the .c files? They become pretty simple after this patch is a

Re: [Mingw-w64-public] [Patch] Issues with vsscanf - first draft

2016-07-07 Thread Ozkan Sezer
On 7/8/16, dw wrote: > On 7/7/2016 4:06 PM, Ozkan Sezer wrote: >> Two copies of this message arrived: the one from your yahoo >> account is sent to spam folder by gmail and doesn't have the >> patch. The one from your limegreensocks went properly into the >> inbox and does have the patch. Somethi

Re: [Mingw-w64-public] [Patch] Issues with vsscanf - first draft

2016-07-07 Thread dw
On 7/7/2016 4:06 PM, Ozkan Sezer wrote: > Two copies of this message arrived: the one from your yahoo > account is sent to spam folder by gmail and doesn't have the > patch. The one from your limegreensocks went properly into the > inbox and does have the patch. Something to do with yahoo > perhap

Re: [Mingw-w64-public] [Patch] Issues with vsscanf - first draft

2016-07-07 Thread Ozkan Sezer
On 7/8/16, dw wrote: > On 7/7/2016 6:45 AM, Ozkan Sezer wrote: >> On 7/7/16, dw wrote: >>> I was looking to see if there was any more inline asm that could be >>> removed from mingw-w64. That brought me to vsscanf (and friends). This >>> looked to be a messy bit of code that could probably use a

Re: [Mingw-w64-public] [Patch] Issues with vsscanf - first draft

2016-07-07 Thread dw
On 7/7/2016 6:45 AM, Ozkan Sezer wrote: On 7/7/16, dw wrote: I was looking to see if there was any more inline asm that could be removed from mingw-w64. That brought me to vsscanf (and friends). This looked to be a messy bit of code that could probably use a review. As I started looking throu

Re: [Mingw-w64-public] [Patch] Issues with vsscanf - first draft

2016-07-07 Thread Ozkan Sezer
On 7/7/16, dw wrote: > I was looking to see if there was any more inline asm that could be > removed from mingw-w64. That brought me to vsscanf (and friends). This > looked to be a messy bit of code that could probably use a review. > > As I started looking through it, I found what I believe to b

[Mingw-w64-public] [Patch] Issues with vsscanf - first draft

2016-07-07 Thread dw
I was looking to see if there was any more inline asm that could be removed from mingw-w64. That brought me to vsscanf (and friends). This looked to be a messy bit of code that could probably use a review. As I started looking through it, I found what I believe to be a bunch of flaws (see ht