From: Andi Kleen <ak@suse.de>
To: "Jan Beulich" <jbeulich@novell.com>, sam@ravnborg.org
Cc: "Michael Matz" <matz@suse.de>,
"Richard Guenther" <rguenther@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [development-gcc] Re: do_exit stuck
Date: Tue, 12 Sep 2006 08:32:06 +0200 [thread overview]
Message-ID: <200609120832.06645.ak@suse.de> (raw)
In-Reply-To: <4506767D.76E4.0078.0@novell.com>
On Tuesday 12 September 2006 08:57, Jan Beulich wrote:
> >Isn't a Kconfig patch missing? I don't see any place that defines
> >CONFIG_AS_CFI_SIGNAL_FRAME. Actually Kconfig wouldn't
> >be very good for this, so auto testing would be preferable
> >(like the cfi test is doing)
>
> Using that framework was the intention (you used a CONFIG_
> prefix there, and so did I), but as I wasn't sure about its status,
> and as I also was doing this against plain 2.6.18-rc6, I didn't add
> the actual detection logic. Actually I also think that should be
> done a little differently to allow for better future extension, i.e.
> instead of adding to CFLAGS store the auto-detected results in
> a header and forcibly -include it.
Ok. I guess I'll do it in the same way as the CFI detection
and maybe one of the kbuild folks can figure out a better way longer term.
BTW which binutils release started supporting this properly?
-Andi
next prev parent reply other threads:[~2006-09-12 8:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200608291332.18499.ak@suse.de>
[not found] ` <Pine.LNX.4.64.0608301626150.6582@wotan.suse.de>
[not found] ` <44F5CAD0.76E4.0078.0@novell.com>
[not found] ` <200608301740.41729.ak@suse.de>
2006-09-11 15:37 ` [development-gcc] Re: do_exit stuck Jan Beulich
2006-09-11 20:17 ` Andi Kleen
2006-09-12 6:57 ` Jan Beulich
2006-09-12 6:32 ` Andi Kleen [this message]
2006-09-12 8:35 ` Jakub Jelinek
2006-09-12 8:45 ` Jan Beulich
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=200609120832.06645.ak@suse.de \
--to=ak@suse.de \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matz@suse.de \
--cc=rguenther@suse.de \
--cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.