Thanks!
On 7/19/06, Mike McCormack <[EMAIL PROTECTED]> wrote:
I investigated this and have reported a bug:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28437
In summary, gcc 4.1.2 seems to ignore all but the last -fno-builtin-*
flag out of many...
$ cat b.c
int iswalpha(unsigned short);
$ gcc
I investigated this and have reported a bug:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28437
In summary, gcc 4.1.2 seems to ignore all but the last -fno-builtin-*
flag out of many...
$ cat b.c
int iswalpha(unsigned short);
$ gcc -fno-builtin-iswalpha -c b.c
$ gcc -fno-builtin-iswalpha -fno
Mike McCormack wrote:
Can you file a bug report at
http://gcc.gnu.org/bugzilla/
You're welcome to file a bug report if you like, but I don't consider
this worth of one myself.
Oh. A gcc bug report. I really should read my mail more carefully :)
I was considering that, bug I didn't have
Dan Kegel wrote:
gcc 4.1.1 seems to have a bug or some new "feature" in that it still
warns about builtin iswalpha, etc having a different prototype to the
msvcrt functions with the same name, even when -fno-builtin-iswalpha is
specified.
It seems to behave when -fno-builtin is specified though
On 7/19/06, Mike McCormack <[EMAIL PROTECTED]> wrote:
gcc 4.1.1 seems to have a bug or some new "feature" in that it still
warns about builtin iswalpha, etc having a different prototype to the
msvcrt functions with the same name, even when -fno-builtin-iswalpha is
specified.
It seems to behave w
