[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220502195251.5d862365@rorschach.local.home>
Date: Mon, 2 May 2022 19:52:51 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Christophe Leroy <christophe.leroy@...roup.eu>
Cc: "Naveen N. Rao" <naveen.n.rao@...ux.vnet.ibm.com>,
"llvm@...ts.linux.dev" <llvm@...ts.linux.dev>,
Nick Desaulniers <ndesaulniers@...gle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Nathan Chancellor <nathan@...nel.org>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>
Subject: Re: [PATCH 2/2] recordmcount: Handle sections with no non-weak
symbols
On Mon, 2 May 2022 14:44:56 +0000
Christophe Leroy <christophe.leroy@...roup.eu> wrote:
> If we do that after the linking, won't it be a nightmare with the
> trampolines installed by the linker when the destination is over the 24
> bits limit ?
Not sure what you mean. The locations I'm talking about is the full
address saved in the __mcount_loc table (data section).
-- Steve
Powered by blists - more mailing lists