From: Timmy Douglas <timmy+lkml@cc.gatech.edu>
To: Brian Gerst <bgerst@didntduck.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: macro in linux/compiler.h pollutes gcc __attribute__ namespace
Date: Wed, 04 May 2005 14:10:21 -0400 [thread overview]
Message-ID: <87fyx2vp4i.fsf@mail.gatech.edu> (raw)
In-Reply-To: <42790A86.9070002@didntduck.org> (Brian Gerst's message of "Wed, 04 May 2005 13:46:46 -0400")
Brian Gerst <bgerst@didntduck.org> writes:
> Timmy Douglas wrote:
>> (I'm not subscribed so please CC me replies that you want me to reply
>> to.)
>> Recently I've found a problem with emacs where gcc optimizes a
>> function to be inline where it shouldn't be. The emacs developers use
>> a macro like this:
>>[snip]
>> I've realized that this file includes linux/compiler.h which does:
>> 139
>> 140 #ifndef noinline
>> 141 #define noinline
>> 142 #endif
>> 143
>>[snip]
>
> The right question to be asking is why is emacs including kernel headers?
I'm guessing it goes sort of like this:
signal.h -> bits/sigcontext.h -> asm/sigcontext.h -> linux/compiler.h
next prev parent reply other threads:[~2005-05-04 18:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 17:35 macro in linux/compiler.h pollutes gcc __attribute__ namespace Timmy Douglas
2005-05-04 17:46 ` Brian Gerst
2005-05-04 18:10 ` Timmy Douglas [this message]
2005-05-04 20:55 ` Kyle Moffett
2005-05-05 2:08 ` Timmy Douglas
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=87fyx2vp4i.fsf@mail.gatech.edu \
--to=timmy+lkml@cc.gatech.edu \
--cc=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.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: link
Be 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