From: Andi Kleen <ak@suse.de>
To: jbeulich@novell.com, patches@x86-64.org,
linux-kernel@vger.kernel.org, stable@kernel.org
Subject: [PATCH 2.6.22] [2/5] x86_64: Check for .cfi_rel_offset in CFI probe
Date: Wed, 15 Aug 2007 12:38:55 +0200 (CEST) [thread overview]
Message-ID: <20070815103855.5338A14F28@wotan.suse.de> (raw)
In-Reply-To: <200708151238.148026000@suse.de>
Very old binutils have .cfi_startproc/endproc, but
no .cfi_rel_offset. Check for .cfi_rel_offset too.
Cc: jbeulich@novell.com
---
arch/i386/Makefile | 4 ++--
arch/x86_64/Makefile | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
Index: linux-2.6.22-stable/arch/x86_64/Makefile
===================================================================
--- linux-2.6.22-stable.orig/arch/x86_64/Makefile
+++ linux-2.6.22-stable/arch/x86_64/Makefile
@@ -57,8 +57,8 @@ cflags-y += $(call cc-option,-mno-sse -m
cflags-y += -maccumulate-outgoing-args
# do binutils support CFI?
-cflags-y += $(call as-instr,.cfi_startproc\n.cfi_endproc,-DCONFIG_AS_CFI=1,)
-AFLAGS += $(call as-instr,.cfi_startproc\n.cfi_endproc,-DCONFIG_AS_CFI=1,)
+cflags-y += $(call as-instr,.cfi_startproc\n.cfi_rel_offset rsp${comma}0\n.cfi_endproc,-DCONFIG_AS_CFI=1,)
+AFLAGS += $(call as-instr,.cfi_startproc\n.cfi_rel_offset rsp${comma}0\n.cfi_endproc,-DCONFIG_AS_CFI=1,)
# is .cfi_signal_frame supported too?
cflags-y += $(call as-instr,.cfi_startproc\n.cfi_signal_frame\n.cfi_endproc,-DCONFIG_AS_CFI_SIGNAL_FRAME=1,)
Index: linux-2.6.22-stable/arch/i386/Makefile
===================================================================
--- linux-2.6.22-stable.orig/arch/i386/Makefile
+++ linux-2.6.22-stable/arch/i386/Makefile
@@ -51,8 +51,8 @@ cflags-y += -maccumulate-outgoing-args
CFLAGS += $(shell if [ $(call cc-version) -lt 0400 ] ; then echo $(call cc-option,-fno-unit-at-a-time); fi ;)
# do binutils support CFI?
-cflags-y += $(call as-instr,.cfi_startproc\n.cfi_endproc,-DCONFIG_AS_CFI=1,)
-AFLAGS += $(call as-instr,.cfi_startproc\n.cfi_endproc,-DCONFIG_AS_CFI=1,)
+cflags-y += $(call as-instr,.cfi_startproc\n.cfi_rel_offset esp${comma}0\n.cfi_endproc,-DCONFIG_AS_CFI=1,)
+AFLAGS += $(call as-instr,.cfi_startproc\n.cfi_rel_offset esp${comma}0\n.cfi_endproc,-DCONFIG_AS_CFI=1,)
# is .cfi_signal_frame supported too?
cflags-y += $(call as-instr,.cfi_startproc\n.cfi_signal_frame\n.cfi_endproc,-DCONFIG_AS_CFI_SIGNAL_FRAME=1,)
next prev parent reply other threads:[~2007-08-15 10:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 10:38 [PATCH 2.6.22] [0/5] x86 updates for 2.6.22-stable Andi Kleen
2007-08-15 10:38 ` [PATCH 2.6.22] [1/5] i386: allow debuggers to access the vsyscall page with compat vDSO Andi Kleen
2007-08-15 10:38 ` Andi Kleen [this message]
2007-08-15 10:38 ` [PATCH 2.6.22] [3/5] x86_64: Change PMDS invocation to single macro Andi Kleen
2007-08-15 10:38 ` [PATCH 2.6.22] [4/5] i386: Fix double fault handler Andi Kleen
2007-08-15 10:38 ` [PATCH 2.6.22] [5/5] i386: Handle P6s without performance counters in nmi watchdog 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=20070815103855.5338A14F28@wotan.suse.de \
--to=ak@suse.de \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@x86-64.org \
--cc=stable@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
all inboxes | Powered by JetHome®