public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mike at codeweavers dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/28437] New: multiple fno-builtin-* flags broken Date: Wed, 19 Jul 2006 15:21:00 -0000 [thread overview] Message-ID: <bug-28437-11334@http.gcc.gnu.org/bugzilla/> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1601 bytes --] If more than one -fno-builtin-* flag is specified, the first one is ignored. I've seen other reports of this on Wine the mailing lists. We use -fno-builtin to supress the gcc builtins that are incompatible with msvcrt's string functions. mike@black:~/wine$ cat b.c int iswalpha(unsigned short); mike@black:~/wine$ gcc -fno-builtin-iswalpha -c b.c mike@black:~/wine$ gcc -fno-builtin-iswalpha -fno-builtin-iswalnum -c b.c b.c:1: warning: conflicting types for built-in function iswalpha mike@black:~/wine$ gcc -v Using built-in specs. Target: x86_64-linux-gnu Configured with: ../src/configure -v --enable-languages=c,c++,fortran,objc,obj-c++,ada,treelang --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --program-suffix=-4.1 --enable-__cxa_atexit --enable-clocale=gnu --enable-libstdcxx-debug --enable-mpfr --enable-checking=release x86_64-linux-gnu Thread model: posix gcc version 4.1.2 20060715 (prerelease) (Debian 4.1.1-9) mike@black:~/wine$ uname -a Linux black 2.6.16.11 #1 Mon May 1 16:44:30 KST 2006 x86_64 GNU/Linux -- Summary: multiple fno-builtin-* flags broken Product: gcc Version: 4.1.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mike at codeweavers dot com GCC build triplet: x86_64-linux-gnu GCC host triplet: x86_64-linux-gnu GCC target triplet: x86_64-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28437
next reply other threads:[~2006-07-19 15:21 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-07-19 15:21 mike at codeweavers dot com [this message] 2006-07-19 15:31 ` [Bug c/28437] [4.1/4.2 Regression] " pinskia at gcc dot gnu dot org 2006-07-20 22:29 ` pinskia at gcc dot gnu dot org 2006-07-24 5:46 ` steven at gcc dot gnu dot org 2006-07-24 5:55 ` [Bug driver/28437] " pinskia at gcc dot gnu dot org 2006-07-24 5:56 ` pinskia at gcc dot gnu dot org 2006-07-24 15:42 ` hjl at lucon dot org 2006-07-24 20:52 ` steven at gcc dot gnu dot org 2006-07-24 21:46 ` steven at gcc dot gnu dot org 2006-07-24 21:47 ` [Bug driver/28437] [4.2 " steven at gcc dot gnu dot org 2006-07-24 21:51 ` steven at gcc dot gnu dot org 2006-07-24 22:14 ` steven at gcc dot gnu dot org 2006-07-24 22:15 ` pinskia at gcc dot gnu dot org 2006-07-25 0:36 ` hjl at lucon dot org 2006-07-27 21:27 ` hjl at gcc dot gnu dot org 2006-07-31 23:32 ` mmitchel at gcc dot gnu dot org 2006-07-31 23:33 ` pinskia at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-28437-11334@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).