public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "malitzke at metronets dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/27528] compiling linux kernels 2.6.16.14/15 2.6.17-rc3 on powerpc (7450) get error on long exixting code Date: Wed, 10 May 2006 14:44:00 -0000 [thread overview] Message-ID: <20060510144349.25355.qmail@sourceware.org> (raw) In-Reply-To: <bug-27528-11706@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from malitzke at metronets dot com 2006-05-10 14:43 ------- To A Pinski While I am _not_ a C lawyer, the following seems pertinent: 1 __FUNCTION__ is _not_ a predefined macro. However __func__ a predefined identifier and I will take this up with the kernel people. However, even changing__FUNCTION__ to __func__ still produces an error. Let the language lawyer sort this out. 2 Taking __FUNCTION__ entirely out of the original Macro Definition and using all of the kernel paraphernalia produces valid code. Out of that context I can not get even __FILE__ to work properly; only __line__ 3 Your "Hi" misses the point because it is certainly not a predefined macro and not even a predefined identifier. Therefore the comparison seems invalid to me. I am reopening this because I believe that the raised by "__func__" should be addressed. Also it is not the first time that the kernel people found ways to get GCC closer to the standards. -- malitzke at metronets dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dje at gcc dot gnu dot org Status|RESOLVED |UNCONFIRMED Resolution|INVALID | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27528
next prev parent reply other threads:[~2006-05-10 14:44 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-05-10 2:44 [Bug c/27528] New: " malitzke at metronets dot com 2006-05-10 3:05 ` [Bug c/27528] " malitzke at metronets dot com 2006-05-10 4:04 ` [Bug middle-end/27528] " pinskia at gcc dot gnu dot org 2006-05-10 5:24 ` pinskia at gcc dot gnu dot org 2006-05-10 5:30 ` pinskia at gcc dot gnu dot org 2006-05-10 14:44 ` malitzke at metronets dot com [this message] 2006-05-10 14:56 ` dje at gcc dot gnu dot org 2006-05-10 15:06 ` pinskia at gcc dot gnu dot org 2006-05-10 20:17 ` malitzke at metronets dot com 2006-05-10 20:41 ` pinskia at gcc dot gnu dot org 2006-06-14 15:09 ` hp at gcc dot gnu dot org 2006-06-14 15:09 ` hp at gcc dot gnu dot org 2006-06-15 3:26 ` malitzke at metronets dot com 2006-06-15 17:15 ` hp at gcc dot gnu dot org 2006-06-15 23:03 ` malitzke at metronets dot com 2006-06-15 23:03 ` Andrew Pinski 2006-06-15 23:07 ` pinskia at physics dot uc dot edu 2006-10-27 5:24 ` pinskia at gcc dot gnu dot org 2006-11-03 13:23 ` rsandifo at gcc dot gnu dot org 2006-11-03 13:27 ` hp at gcc dot gnu dot org 2006-11-03 13:30 ` rsandifo at gcc dot gnu dot org 2006-11-09 9:34 ` rsandifo at gcc dot gnu dot org 2006-11-11 9:47 ` rsandifo at gcc dot gnu dot org 2006-11-11 9:53 ` rsandifo at gcc dot gnu dot org 2006-11-11 9:54 ` rsandifo at gcc dot gnu dot org 2006-12-01 1:07 ` chaoyingfu at gcc dot gnu dot org 2007-01-10 19:14 ` [Bug middle-end/27528] [4.2/4.3 Regression] " 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=20060510144349.25355.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).