Skip to contentSkip to conversation

ia64: linux-next allmodconfig

DISCUSSION Andrew Morton 4 participants 4 messages Nov 20, 2008

lore
Share & tools
lore
#0 lore raw

arch/ia64/kernel/built-in.o(.text+0x4a22): In function `efi_initialize_iomem_resources':
: undefined reference to __ia64_save_stack_nonlocal' arch/ia64/kernel/built-in.o(.text+0x16262): In function pfm_context_create':
: undefined reference to __ia64_save_stack_nonlocal' arch/ia64/kernel/built-in.o(.text+0x238a2): In function sys_perfmonctl':
: undefined reference to __ia64_save_stack_nonlocal' arch/ia64/kernel/built-in.o(.text+0x466c2): In function dup_state_stack':
: undefined reference to __ia64_save_stack_nonlocal' arch/ia64/kernel/built-in.o(.text+0x46cf2): In function desc_prologue':
: undefined reference to __ia64_save_stack_nonlocal' arch/ia64/kernel/built-in.o(.text+0x49752): more undefined references to __ia64_save_stack_nonlocal' follow

Whatever caused this is fairly well hidden from `grep'..

#1 lore raw
Quoted 13 lines · Andrew Morton

arch/ia64/kernel/built-in.o(.text+0x4a22): In function `efi_initialize_iomem_resources':
: undefined reference to __ia64_save_stack_nonlocal' arch/ia64/kernel/built-in.o(.text+0x16262): In function pfm_context_create':
: undefined reference to __ia64_save_stack_nonlocal' arch/ia64/kernel/built-in.o(.text+0x238a2): In function sys_perfmonctl':
: undefined reference to __ia64_save_stack_nonlocal' arch/ia64/kernel/built-in.o(.text+0x466c2): In function dup_state_stack':
: undefined reference to __ia64_save_stack_nonlocal' arch/ia64/kernel/built-in.o(.text+0x46cf2): In function desc_prologue':
: undefined reference to __ia64_save_stack_nonlocal' arch/ia64/kernel/built-in.o(.text+0x49752): more undefined references to __ia64_save_stack_nonlocal' follow

Quoted 2 lines

Whatever caused this is fairly well hidden from `grep'..

That looks like some builtin function that gcc might add. I've seen other types of references before like that on x86. Can't remember what it was exactly, but it hit me when I had two slightly different compilers in my distcc farm.

/me goes looks at his http://rostedt.homelinux.com/distcc/ page.

Ah, here it is...

Found that -fstack-protect-all set will cause the cross compiler to create "stack_chk_guard" calls. These are not defined in the kernel and cause linking problems.

Not sure if __ia64_save_stack_nonlocal is equivalent, but perhaps it is related. Maybe some CFLAG was set that caused an issue?

-- Steve

#2 lore raw
In reply to Andrew Morton
Quoted 4 lines

That looks like some builtin function that gcc might add. I've seen other types of references before like that on x86. Can't remember what it was exactly, but it hit me when I had two slightly different compilers in my distcc farm.

Hmmm. I don't see this with "next-2008119" compiled with gcc 4.3.1

-Tony

#3 lore raw
In reply to Andrew Morton
Quoted 3 lines · Andrew Morton

arch/ia64/kernel/built-in.o(.text+0x4a22): In function `efi_initialize_iomem_resources':
: undefined reference to __ia64_save_stack_nonlocal' arch/ia64/kernel/built-in.o(.text+0x16262): In function pfm_context_create':

From gcc/config/ia64/ia64.md:

    ;; Non-local goto support.

    (define_expand "save_stack_nonlocal"
      [(use (match_operand:OI 0 "memory_operand" ""))
       (use (match_operand:DI 1 "register_operand" ""))]
      ""
    {
      emit_library_call (gen_rtx_SYMBOL_REF (Pmode,
                                             \"__ia64_save_stack_nonlocal\"),
                         0, VOIDmode, 2, XEXP (operands[0], 0), Pmode,
                         operands[1], Pmode);
      DONE;
    })

Generated by __builtin_update_setjmp_buf, defined in libgcc.

Andreas.

Signature · 4 lines
Andreas Schwab, SuSE Labs, [email protected]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."