From: "Arnd Bergmann" <arnd@arndb.de>
To: "Yuntao Liu" <liuyuntao12@huawei.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: "Russell King" <linux@armlinux.org.uk>,
"Andrew Davis" <afd@ti.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Jonathan Corbet" <corbet@lwn.net>,
"Mike Rapoport" <rppt@kernel.org>,
"Eric DeVolder" <eric.devolder@oracle.com>,
"Rob Herring" <robh@kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Linus Walleij" <linus.walleij@linaro.org>
Subject: Re: [PATCH -next] arm32: enable HAVE_LD_DEAD_CODE_DATA_ELIMINATION
Date: Thu, 22 Feb 2024 17:04:43 +0100 [thread overview]
Message-ID: <58297ee9-4f33-4b3b-bd00-b44e86965892@app.fastmail.com> (raw)
In-Reply-To: <4e9396ca-460b-49ca-818e-73f0a8997b15@huawei.com>
On Thu, Feb 22, 2024, at 12:24, liuyuntao (F) wrote:
>
> The position of the caret has been moved below the right brace
> of { KEEP(*(.vectors.bhb.loop8)) }, indicating that lld is treating
> the entire `KEEP(*(.vectors))` as a file name. This could potentially be
> a bug in lld. Perhaps we can temporarily
> enable the DCE option only when option LD_IS_LLD is disabled,
> like risc-v:
>
> `select HAVE_LD_DEAD_CODE_DATA_ELIMINATION if !LD_IS_LLD`.
I would really like to see this working with lld if at all
possible, as it allows the combination of gc-sections with
lto and CONFIG_TRIM_UNUSED_KSYMS.
I experimented with lld myself now and I did get a booting
kernel even without the the KEEP() on the vectors. I also
see that this is the only use of OVERLAY in the kernel, so
I hope that we can find a way to make it work with existing
lld after all, either without the KEEP or without the OVERLAY.
Did you see any problems without the KEEP() on the vectors?
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Yuntao Liu" <liuyuntao12@huawei.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: "Russell King" <linux@armlinux.org.uk>,
"Andrew Davis" <afd@ti.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Jonathan Corbet" <corbet@lwn.net>,
"Mike Rapoport" <rppt@kernel.org>,
"Eric DeVolder" <eric.devolder@oracle.com>,
"Rob Herring" <robh@kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Linus Walleij" <linus.walleij@linaro.org>
Subject: Re: [PATCH -next] arm32: enable HAVE_LD_DEAD_CODE_DATA_ELIMINATION
Date: Thu, 22 Feb 2024 17:04:43 +0100 [thread overview]
Message-ID: <58297ee9-4f33-4b3b-bd00-b44e86965892@app.fastmail.com> (raw)
In-Reply-To: <4e9396ca-460b-49ca-818e-73f0a8997b15@huawei.com>
On Thu, Feb 22, 2024, at 12:24, liuyuntao (F) wrote:
>
> The position of the caret has been moved below the right brace
> of { KEEP(*(.vectors.bhb.loop8)) }, indicating that lld is treating
> the entire `KEEP(*(.vectors))` as a file name. This could potentially be
> a bug in lld. Perhaps we can temporarily
> enable the DCE option only when option LD_IS_LLD is disabled,
> like risc-v:
>
> `select HAVE_LD_DEAD_CODE_DATA_ELIMINATION if !LD_IS_LLD`.
I would really like to see this working with lld if at all
possible, as it allows the combination of gc-sections with
lto and CONFIG_TRIM_UNUSED_KSYMS.
I experimented with lld myself now and I did get a booting
kernel even without the the KEEP() on the vectors. I also
see that this is the only use of OVERLAY in the kernel, so
I hope that we can find a way to make it work with existing
lld after all, either without the KEEP or without the OVERLAY.
Did you see any problems without the KEEP() on the vectors?
Arnd
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-02-22 16:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 8:15 [PATCH -next] arm32: enable HAVE_LD_DEAD_CODE_DATA_ELIMINATION Yuntao Liu
2024-02-20 8:15 ` Yuntao Liu
2024-02-20 8:40 ` Arnd Bergmann
2024-02-20 8:40 ` Arnd Bergmann
2024-02-20 9:53 ` liuyuntao (F)
2024-02-20 9:53 ` liuyuntao (F)
2024-02-21 15:51 ` Arnd Bergmann
2024-02-21 15:51 ` Arnd Bergmann
2024-02-22 9:52 ` Arnd Bergmann
2024-02-22 9:52 ` Arnd Bergmann
2024-02-22 11:32 ` liuyuntao (F)
2024-02-22 11:32 ` liuyuntao (F)
2024-02-22 11:24 ` liuyuntao (F)
2024-02-22 11:24 ` liuyuntao (F)
2024-02-22 16:04 ` Arnd Bergmann [this message]
2024-02-22 16:04 ` Arnd Bergmann
2024-02-23 1:39 ` liuyuntao (F)
2024-02-23 1:39 ` liuyuntao (F)
2024-02-23 6:32 ` Arnd Bergmann
2024-02-23 6:32 ` Arnd Bergmann
2024-02-27 8:06 ` liuyuntao (F)
2024-02-27 8:06 ` liuyuntao (F)
2024-03-07 3:09 ` liuyuntao (F)
2024-03-07 3:09 ` liuyuntao (F)
2024-03-07 7:29 ` Arnd Bergmann
2024-03-07 7:29 ` Arnd Bergmann
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=58297ee9-4f33-4b3b-bd00-b44e86965892@app.fastmail.com \
--to=arnd@arndb.de \
--cc=afd@ti.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=eric.devolder@oracle.com \
--cc=geert+renesas@glider.be \
--cc=kirill.shutemov@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=liuyuntao12@huawei.com \
--cc=robh@kernel.org \
--cc=rppt@kernel.org \
--cc=tglx@linutronix.de \
/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.