From: Andi Kleen <ak@suse.de>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Jan Beulich <jbeulich@novell.com>, Andrew Morton <akpm@osdl.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [patch 1/2] i386: add CFI macros for stack manipulation
Date: Fri, 28 Jul 2006 20:36:45 +0200 [thread overview]
Message-ID: <200607282036.45608.ak@suse.de> (raw)
In-Reply-To: <200607281353_MC3-1-C662-536D@compuserve.com>
On Friday 28 July 2006 19:50, Chuck Ebbert wrote:
> Add macros to dwarf2.h to simplify pushing and popping stack
> variables.
I feared someone would do that patch. I've thought about it myself.
However it's not a good idea. I've already had complaints that some code in
x86-64 is too hard to read/debug because it uses too many macros. I think
it's better if the core core still uses "real" instructions and keep the
CFI_* stuff as annotation that most people can just ignore.
With your change that wouldn't be the case and everybody hacking
the code would need to know all of CFI too, which is still quite arcane
stuff.
So while it would make the source shorter and require less typing
I don't think it's good for readability.
What would be a good thing if someone could write it up would
be a short tutorial for Documentation/* on CFI
-Andi
next prev parent reply other threads:[~2006-07-28 18:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 17:50 [patch 1/2] i386: add CFI macros for stack manipulation Chuck Ebbert
2006-07-28 18:36 ` Andi Kleen [this message]
2006-07-28 19:40 Chuck Ebbert
2006-07-28 19:59 ` Andi Kleen
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=200607282036.45608.ak@suse.de \
--to=ak@suse.de \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).