From: Andi Kleen <ak@suse.de>
To: "Jan Beulich" <JBeulich@novell.com>
Cc: discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: [discuss] [PATCH] allow CONFIG_FRAME_POINTER for x86-64
Date: Fri, 9 Sep 2005 11:23:58 +0200 [thread overview]
Message-ID: <200509091123.59205.ak@suse.de> (raw)
In-Reply-To: <43216EFB020000780002489B@emea1-mh.id2.novell.com>
On Friday 09 September 2005 11:16, Jan Beulich wrote:
> >>> Andi Kleen <ak@suse.de> 09.09.05 10:54:11 >>>
> >
> >On Thursday 08 September 2005 18:04, Jan Beulich wrote:
> >> (Note: Patch also attached because the inline version is certain to
>
> get
>
> >> line wrapped.)
> >>
> >> Allow building the x86-64 kernels with frame pointers if so needed.
> >
> >This doesn't work because you would need to pass
>
> -fno-omit-frame-pointer
>
> >somewhere.
>
> So is done in the top-level makefile.
Indeed. Someone must have fixed it. But why would anyone want frame pointers
on x86-64?
-Andi
next prev parent reply other threads:[~2005-09-09 9:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 16:04 [PATCH] allow CONFIG_FRAME_POINTER for x86-64 Jan Beulich
2005-09-09 8:54 ` [discuss] " Andi Kleen
2005-09-09 9:16 ` Jan Beulich
2005-09-09 9:23 ` Andi Kleen [this message]
2005-09-09 9:40 ` Jan Beulich
2005-09-09 10:45 ` Hugh Dickins
2005-09-09 10:58 ` Andi Kleen
2005-09-09 11:14 ` Hugh Dickins
2005-09-09 11:21 ` Andi Kleen
2005-09-09 11:31 ` Hugh Dickins
2005-09-09 11:42 ` Andi Kleen
2005-09-09 12:00 ` Hugh Dickins
2005-09-09 17:19 ` Alexander Nyberg
2005-09-10 5:13 ` Andrew Morton
2005-09-10 6:12 ` Andi Kleen
2005-09-09 11:07 ` Philippe Elie
2005-09-09 11:19 ` Andi Kleen
2005-09-09 12:41 ` Eric Dumazet
-- strict thread matches above, loose matches on Subject: below --
2005-09-09 17:50 Chuck Ebbert
2005-09-10 0:16 ` 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=200509091123.59205.ak@suse.de \
--to=ak@suse.de \
--cc=JBeulich@novell.com \
--cc=discuss@x86-64.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 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.