Hi all,
After merging the powerpc tree, today's (it may have been yesterday's)
linux-next build (powerpc allyesconfig) produced this warning:
WARNING: modpost: vmlinux: section mismatch in reference: fadump_setup_param_area+0x200 (section: .text.fadump_setup_param_area) -> memblock_phys_alloc_range (section: .init.text)
Introduced by commit
683eab94da75 ("powerpc/fadump: setup additional parameters for dump capture kernel")
--
Cheers,
Stephen Rothwell
Stephen Rothwell <[email protected]> writes:
> Hi all,
>
> After merging the powerpc tree, today's (it may have been yesterday's)
> linux-next build (powerpc allyesconfig) produced this warning:
>
> WARNING: modpost: vmlinux: section mismatch in reference: fadump_setup_param_area+0x200 (section: .text.fadump_setup_param_area) -> memblock_phys_alloc_range (section: .init.text)
I don't see the warning, but clearly it is possible if the compiler
decides not to inline fadump_setup_param_area().
What compiler version are you using?
cheers
Hi Michael,
On Thu, 16 May 2024 12:42:01 +1000 Michael Ellerman <[email protected]> wrote:
>
> Stephen Rothwell <[email protected]> writes:
> >
> > After merging the powerpc tree, today's (it may have been yesterday's)
> > linux-next build (powerpc allyesconfig) produced this warning:
> >
> > WARNING: modpost: vmlinux: section mismatch in reference: fadump_setup_param_area+0x200 (section: .text.fadump_setup_param_area) -> memblock_phys_alloc_range (section: .init.text)
>
> I don't see the warning, but clearly it is possible if the compiler
> decides not to inline fadump_setup_param_area().
>
> What compiler version are you using?
$ gcc --version
gcc (Debian 13.2.0-7) 13.2.0
(on zz1 if you want to test)
--
Cheers,
Stephen Rothwell