On Mon, Sep 22, 2008 at 5:27 AM, Francois Gouget <[EMAIL PROTECTED]> wrote:
> On Sat, 20 Sep 2008, Michael Karcher wrote:
> [...]
>> Looks like we need to compile with -fno-builtin-sscanf, because gcc
>> knows the implementation of glibc's sscanf, and you explicitly have to
>> forbid it to use this
On Sat, 20 Sep 2008, Michael Karcher wrote:
[...]
> Looks like we need to compile with -fno-builtin-sscanf, because gcc
> knows the implementation of glibc's sscanf, and you explicitly have to
> forbid it to use this knowledge which does not apply perfectly to
> Microsofts sscanf. This (of course)
On Fri, Sep 19, 2008 at 03:51:00PM -0700, Dan Kegel wrote:
> Here's the gcc error:
> > scanf.c:66: warning: unknown conversion type character `P' in format
>
> I'm not a programmer, but I play one on TV. And here's what I
> came up with in five minutes of typing and not enough thinking:
>
> That
Michael Karcher <[EMAIL PROTECTED]> writes:
> Sorry, I didn't manage to write what I mean. The only dll modules in the
> wine tree that currently use @BUILTINFLAG@ (and include msvcrt headers)
> are the two I listed. And after examing the little amount of C code they
> contain, I see no problem to
Am Sonntag, den 21.09.2008, 13:46 +0200 schrieb Alexandre Julliard:
> Michael Karcher <[EMAIL PROTECTED]> writes:
>
> > Am Sonntag, den 21.09.2008, 13:07 +0200 schrieb Alexandre Julliard:
> >> If performance is an issue you most likely don't want to use msvcrt at
> >> all, native Unix libc will al
Michael Karcher <[EMAIL PROTECTED]> writes:
> Am Sonntag, den 21.09.2008, 13:07 +0200 schrieb Alexandre Julliard:
>> If performance is an issue you most likely don't want to use msvcrt at
>> all, native Unix libc will always be faster. And knowing MS, they are
>> capable of adding an exception han
Michael Karcher <[EMAIL PROTECTED]> writes:
> Sure I can, this was approach b I suggested. But that may be harmful to
> performance, as it forbids gcc to use any knowledge about the standard
> library (includes inlining of memcpy with small constant sizes or
> built-in pureness annotations).
If p
Am Sonntag, den 21.09.2008, 13:07 +0200 schrieb Alexandre Julliard:
> Michael Karcher <[EMAIL PROTECTED]> writes:
> > Sure I can, this was approach b I suggested. But that may be harmful to
> > performance, as it forbids gcc to use any knowledge about the standard
> > library (includes inlining of
Am Sonntag, den 21.09.2008, 11:25 +0200 schrieb Alexandre Julliard:
> Michael Karcher <[EMAIL PROTECTED]> writes:
>
> > OK. Thanks for the pointer. I have a configure test ready that checks
> > whether the global -fno-builtin is really needed., and uses separate
> > flags otherwise. I am planning
Michael Karcher <[EMAIL PROTECTED]> writes:
> OK. Thanks for the pointer. I have a configure test ready that checks
> whether the global -fno-builtin is really needed., and uses separate
> flags otherwise. I am planning to submit it in series with a second
> patch that checks for whether -fno-buil
Am Samstag, den 20.09.2008, 12:17 +0200 schrieb Alexandre Julliard:
> The real problem is that the -fno-builtin-xxx option is broken on some
> gcc versions. We used to use it, but we had to switch to a global
> -fno-builtin because of this bug.
OK. Thanks for the pointer. I have a configure test r
On Samstag 20 September 2008, Paul Vriens wrote:
> James Hawkins wrote:
> > On Fri, Sep 19, 2008 at 4:59 PM, Austin English <[EMAIL PROTECTED]> wrote:
> >> Relevant code:
> >>/* check %p with no hex digits */
> >>ok( sscanf("1233", "%p", &ptr) == 1, "sscanf failed\n" );
> >>ok( ptr ==
Michael Karcher <[EMAIL PROTECTED]> writes:
> On the other hand, for the implementation side (msvcrtd and crtdll),
> option c seems attractive to me, because it just disables the stuff we
> need disabled but allows gcc to take full advantage about knowing the C
> standard on functions where msvcrt
Am Samstag, den 20.09.2008, 10:50 +0200 schrieb Michael Karcher:
> Looks like we need to compile with -fno-builtin-sscanf, because gcc
> knows the implementation of glibc's sscanf,
OK, I looked further into it. On Linux, we don't get the warning,
because gcc is called with the sledgehammer option
Am Freitag, den 19.09.2008, 15:51 -0700 schrieb Dan Kegel:
> Here's the gcc error:
> > scanf.c:66: warning: unknown conversion type character `P' in format
> That particular error depends on gcc knowing intimate details of
> sscanf. Unless we teach gcc about the particular sscanf we're
> implemen
On Fri, Sep 19, 2008 at 5:51 PM, Dan Kegel <[EMAIL PROTECTED]> wrote:
> Here's the gcc error:
>> scanf.c:66: warning: unknown conversion type character `P' in format
>
> I'm not a programmer, but I play one on TV. And here's what I
> came up with in five minutes of typing and not enough thinking:
Here's the gcc error:
> scanf.c:66: warning: unknown conversion type character `P' in format
I'm not a programmer, but I play one on TV. And here's what I
came up with in five minutes of typing and not enough thinking:
That particular error depends on gcc knowing intimate details of
sscanf. Un
On Fri, Sep 19, 2008 at 6:14 PM, Paul Vriens <[EMAIL PROTECTED]> wrote:
> James Hawkins wrote:
>>
>> On Fri, Sep 19, 2008 at 4:59 PM, Austin English <[EMAIL PROTECTED]>
>> wrote:
>>>
>>> Relevant code:
>>> /* check %p with no hex digits */
>>> ok( sscanf("1233", "%p", &ptr) == 1, "sscanf failed
James Hawkins wrote:
> On Fri, Sep 19, 2008 at 4:59 PM, Austin English <[EMAIL PROTECTED]> wrote:
>> Relevant code:
>>/* check %p with no hex digits */
>>ok( sscanf("1233", "%p", &ptr) == 1, "sscanf failed\n" );
>>ok( ptr == (void *)0x1233,"sscanf reads %p instead of %x\n", ptr, 0x1233
> Relevant code:
>/* check %p with no hex digits */
>ok( sscanf("1233", "%p", &ptr) == 1, "sscanf failed\n" );
>ok( ptr == (void *)0x1233,"sscanf reads %p instead of %x\n", ptr, 0x1233 );
>
>ok( sscanf("1234", "%P", &ptr) == 1, "sscanf failed\n" );
>ok( ptr == (void *)0x1234,"
On Fri, Sep 19, 2008 at 4:59 PM, Austin English <[EMAIL PROTECTED]> wrote:
>
> Relevant code:
>/* check %p with no hex digits */
>ok( sscanf("1233", "%p", &ptr) == 1, "sscanf failed\n" );
>ok( ptr == (void *)0x1233,"sscanf reads %p instead of %x\n", ptr, 0x1233 );
>
>ok( sscanf("12
On Fri, Sep 19, 2008 at 4:51 PM, James Hawkins <[EMAIL PROTECTED]> wrote:
> On Fri, Sep 19, 2008 at 4:39 PM, Austin English <[EMAIL PROTECTED]> wrote:
>> Found using -Werror (strangely, didn't occur on ubuntu, but does on
>> PC-BSD)...Must be the gcc version.
>>
>
> @@ -63,7 +63,7 @@ static void te
On Fri, Sep 19, 2008 at 4:39 PM, Austin English <[EMAIL PROTECTED]> wrote:
> Found using -Werror (strangely, didn't occur on ubuntu, but does on
> PC-BSD)...Must be the gcc version.
>
@@ -63,7 +63,7 @@ static void test_sscanf( void )
ok( sscanf("1233", "%p", &ptr) == 1, "sscanf failed\n" );
23 matches
Mail list logo
