[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230615084310.GA780@hsinchu15>
Date: Thu, 15 Jun 2023 16:43:11 +0800
From: Nylon Chen <nylon.chen@...ive.com>
To: Conor Dooley <conor.dooley@...rochip.com>
Cc: schwab@...e.de, linux-kernel@...r.kernel.org,
linux-riscv@...ts.infradead.org, jszhang@...nel.org,
ajones@...tanamicro.com, aou@...s.berkeley.edu, palmer@...belt.com,
paul.walmsley@...ive.com, greentime.hu@...ive.com,
zong.li@...ive.com, nylon7717@...il.com
Subject: Re: [PATCH v2] RISC-V: Support 32_PCREL relocation type in kernel
module
On Thu, Jun 15, 2023 at 09:11:33AM +0100, Conor Dooley wrote:
Hi Conor,
> Hey Nylon,
>
> Firstly, no html emails please :/
Sorry, my Gmail settings got messed up. I will be more careful in the future.
>
> On Thu, Jun 15, 2023 at 03:52:27PM +0800, Nylon Chen wrote:
> > Conor Dooley <conor.dooley@...rochip.com<mailto:conor.dooley@...rochip.com>> 於 2023年6月15日 週四 下午3:38寫道:
> > > On Thu, Jun 15, 2023 at 03:23:02PM +0800, Nylon Chen wrote:
> > > > Fix the 'unsupported relocation type' error caused by
> > > > enabling the -fasynchronous-unwind-tables flag,
> > > > which generates relocation types that are not supported.
> > >
> > > What commit adds the -fasynchronous-unwind-tables flag?
> > sorry my description is not correct, please allow me to add
> >
> > I mean, when we use the flag "-fasynchronous-unwind-tables," it generates
> > the relocation type R_RISCV_32_PCCREL. However, this type is currently not
> > supported, so an error will occur.
>
> (snip)
>
> > > Should there be a Fixes: tag for that commit?
>
> > yes, I will do it.
>
> What mainline commit actually enables this flag?
Because LLVM currently has it enabled by default(https://reviews.llvm.org/D145164), it will generate this
relocation type.
>From what I know, GCC will also enable it in the future.
>
> Cheers,
> Conor.
Powered by blists - more mailing lists