public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/32570] Compiling GCC 4.3.0 with CIL instead of using GCC 4.2 or 4.3 finds many warnings that GCC does not report Date: Sun, 01 Jul 2007 08:53:00 -0000 [thread overview] Message-ID: <20070701085246.15141.qmail@sourceware.org> (raw) In-Reply-To: <bug-32570-13830@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from pinskia at gcc dot gnu dot org 2007-07-01 08:52 ------- >/root/downloads/gcc-4_3-trunk/gcc/toplev.c:558: Error: There is a definition already for floor_log2 This is because floor_log2 uses the GNU C "extern inline". >/gcc-4_3-trunk/gcc/config/i386/i386.c:4121: warning: unused parameter 'named' > /gcc-4_3-trunk/gcc/config/i386/i386.c:4402: warning: unused parameter 'valtype' This is a bug in the cilly because they are used, just not used if TARGET_64BIT_MS_ABI is always false which is the reason why GCC does not warn (this is not a preprocessed conditional but instead a compile time conditional). >/gcc-4_3-trunk/gcc/builtins.c:9410: warning: ISO C forbids casting nonscalar to the same type > /gcc-4_3-trunk/gcc/builtins.c:9416: warning: ISO C forbids casting nonscalar to the same type There is no cast there. So this obviously a bug in cilly. So all the warnings you pointed out are really bugs in cilly and not bugs in GCC sources. -- pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32570
next prev parent reply other threads:[~2007-07-01 8:53 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-07-01 5:30 [Bug c/32570] New: " rob1weld at aol dot com 2007-07-01 5:32 ` [Bug c/32570] " rob1weld at aol dot com 2007-07-01 8:53 ` pinskia at gcc dot gnu dot org [this message] 2007-07-07 16:41 ` rob1weld at aol dot com
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=20070701085246.15141.qmail@sourceware.org \ --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).