Thread (10 messages) 10 messages, 5 authors, 2010-05-26

Re: [Patch 1/4] Allow arch-specific cleanup before breakpoint unregistration

From: David Howells <dhowells@redhat.com>
Date: 2010-05-26 09:55:07
Also in: lkml

Possibly related (same subject, not in this thread)

K.Prasad [off-list ref] wrote:
quoted
My understanding is weak function definitions must appear in a different C
file than their call sites to work on some toolchains.
Atleast, there are quite a few precedents inside the Linux kernel for
__weak functions being invoked from the file in which they are defined
(arch_hwblk_init, arch_enable_nonboot_cpus_begin and hw_perf_disable to
name a few).
Moreover the online GCC docs haven't any such constraints mentioned.
I've seen problems in this area.  gcc sometimes inlines a weak function that's
in the same file as the call point.

David
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help