From: "Jan Beulich" <jbeulich@novell.com>
To: "Ingo Molnar" <mingo@elte.hu>, "Andrew Morton" <akpm@osdl.org>,
"AndiKleen" <ak@suse.de>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [build bug] x86_64, -git: Error: unknown pseudo-op: `.cfi_signal_frame'
Date: Mon, 16 Oct 2006 09:00:22 +0200 [thread overview]
Message-ID: <45334A26.76E4.0078.0@novell.com> (raw)
In-Reply-To: <20061015233341.ca644728.akpm@osdl.org>
>>>> Andrew Morton <akpm@osdl.org> 16.10.06 08:33 >>>
>On Mon, 16 Oct 2006 08:10:37 +0200
>Ingo Molnar <mingo@elte.hu> wrote:
>
>>
>> using latest -git i'm getting this build bug on gcc 3.4:
>>
>> arch/x86_64/kernel/entry.S: Assembler messages:
>> arch/x86_64/kernel/entry.S:157: Error: unknown pseudo-op: `.cfi_signal_frame'
>> arch/x86_64/kernel/entry.S:215: Error: unknown pseudo-op: `.cfi_signal_frame'
>> arch/x86_64/kernel/entry.S:333: Error: unknown pseudo-op: `.cfi_signal_frame'
>> arch/x86_64/kernel/entry.S:548: Error: unknown pseudo-op: `.cfi_signal_frame'
>>
>> gcc version 3.4.0 20040129 (Red Hat Linux 3.4.0-0.3)
>>
>> using gcc 4.1 it doesnt happen
>>
>> gcc version 4.1.1 20060525 (Red Hat 4.1.1-1)
>>
>> this is caused by the following commit:
>>
>> commit adf1423698f00d00b267f7dca8231340ce7d65ef
>> Author: Jan Beulich <jbeulich@novell.com>
>> Date: Tue Sep 26 10:52:41 2006 +0200
>>
>> reverting that patch solves the build problem and the resulting kernel
>> builds and boots fine.
>>
>
>That patch has obvious copy-n-paste errors:
>
>i386:
>
> 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,)
>
>+# is .cfi_signal_frame supported too?
>+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,)
>
>So that won't work.
>
>x86_64 appears to get it right:
>
> 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,)
>
>+# 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,)
>+AFLAGS += $(call as-instr,.cfi_startproc\n.cfi_signal_frame\n.cfi_endproc,-DCONFIG_AS_CFI_SIGNAL_FRAME=1,)
>
>Later,
>
>+#ifdef CONFIG_AS_CFI_SIGNAL_FRAME
>+#define CFI_SIGNAL_FRAME .cfi_signal_frame
>+#else
>+#define CFI_SIGNAL_FRAME
>+#endif
>
>but it's obviously not working. Wanna debug it a bit?
That is nothing I added, I suppose Andi did. But the fix is obvious and trivial.
Jan
next prev parent reply other threads:[~2006-10-16 6:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 6:10 [build bug] x86_64, -git: Error: unknown pseudo-op: `.cfi_signal_frame' Ingo Molnar
2006-10-16 6:33 ` Andrew Morton
2006-10-16 7:00 ` Jan Beulich [this message]
2006-10-16 6:36 ` Nicholas Miell
2006-10-16 6:36 ` Ingo Molnar
2006-10-16 6:43 ` Ingo Molnar
2006-10-16 20:06 ` Sam Ravnborg
2006-10-17 9:37 ` Oleg Verych
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=45334A26.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.