From: Vincent Donnefort <vdonnefort@google.com>
To: llvm@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: samitolvanen@google.com, nhuck@google.com,
ndesaulniers@google.com, kernel-team@android.com
Subject: Bug: MODPOST mismatch ignored due to LTO
Date: Thu, 24 Nov 2022 12:31:31 +0000 [thread overview]
Message-ID: <Y39kI3MOtVI5BAnV@google.com> (raw)
Hi all,
It seems that enabling LTO breaks the check for section mismatch in modpost.
If I create on purpose a mismatch here's the output without LTO
check_section_mismatch()
fromsec=.text
tosec=.init.text
sym=kvm_arch_vcpu_create
=> section mismatch in reference: kvm_vm_ioctl_create_vcpu (section: .text) -> kvm_arch_vcpu_create (section: .init.text)
While with LTO:
check_section_mismatch()
fromsec=.text.kvm_vm_ioctl_create_vcpu
tosec=.init.text
sym=kvm_arch_vcpu_create
=> mismatch ignored, the section ".text.kvm_vm_ioctl_create_vcpu" is
unsurprisingly unknown
LTO seems to append the symbol name to the section which is a problem for
modpost.
Is that a known issue?
Thanks,
Vincent
reply other threads:[~2022-11-24 12:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Y39kI3MOtVI5BAnV@google.com \
--to=vdonnefort@google.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=ndesaulniers@google.com \
--cc=nhuck@google.com \
--cc=samitolvanen@google.com \
/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