From: Conor Dooley <conor@kernel.org> To: palmer@dabbelt.com Cc: conor@kernel.org, Conor Dooley <conor.dooley@microchip.com>, nathan@kernel.org, naresh.kamboju@linaro.org, linux-riscv@lists.infradead.org, llvm@lists.linux.dev Subject: [PATCH v1 0/2] RISC-V: avoid build issues for clang/llvm-17 with binutils 2.35 Date: Thu, 23 Feb 2023 22:05:44 +0000 [thread overview] Message-ID: <20230223220546.52879-1-conor@kernel.org> (raw) From: Conor Dooley <conor.dooley@microchip.com> Hey, Here's an attempted (interim?) fix for issues on v5.10 due to the presence of zifencei & zicsr in object files. I'm seeing another issue that only appears with ld from binutils-2.35 & not with ld from binutils-2.37 on riscv/for-next: /stuff/toolchains/binutils-2.35/bin/riscv64-linux-gnu-ld: .init.data has both ordered [`__patchable_function_entries' in init/main.o] and unordered [`.meminit.data' in mm/sparse.o] sections /stuff/toolchains/binutils-2.35/bin/riscv64-linux-gnu-ld: final link failed: bad value But that's far far further on in the build than we were getting before these patches. Even if we end up dealing with the emitted strings a different way [1], I think the first patch here has some value in moving the check to Kconfig so that it's far easier to tell if the toolchain does need/use these extensions from someone's build artifacts. Cheers, Conor. 1 - https://lore.kernel.org/linux-riscv/20230223195112.10489-1-palmer@rivosinc.com/ cc: nathan@kernel.org cc: palmer@dabbelt.com cc: naresh.kamboju@linaro.org cc: linux-riscv@lists.infradead.org cc: llvm@lists.linux.dev Conor Dooley (2): RISC-V: move zicsr/zifencei spec version check to Kconfig RISC-V: make TOOLCHAIN_NEEDS_SPEC_20191213 gas only arch/riscv/Kconfig | 9 +++++++++ arch/riscv/Makefile | 5 +---- 2 files changed, 10 insertions(+), 4 deletions(-) -- 2.39.1 _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org> To: palmer@dabbelt.com Cc: conor@kernel.org, Conor Dooley <conor.dooley@microchip.com>, nathan@kernel.org, naresh.kamboju@linaro.org, linux-riscv@lists.infradead.org, llvm@lists.linux.dev Subject: [PATCH v1 0/2] RISC-V: avoid build issues for clang/llvm-17 with binutils 2.35 Date: Thu, 23 Feb 2023 22:05:44 +0000 [thread overview] Message-ID: <20230223220546.52879-1-conor@kernel.org> (raw) From: Conor Dooley <conor.dooley@microchip.com> Hey, Here's an attempted (interim?) fix for issues on v5.10 due to the presence of zifencei & zicsr in object files. I'm seeing another issue that only appears with ld from binutils-2.35 & not with ld from binutils-2.37 on riscv/for-next: /stuff/toolchains/binutils-2.35/bin/riscv64-linux-gnu-ld: .init.data has both ordered [`__patchable_function_entries' in init/main.o] and unordered [`.meminit.data' in mm/sparse.o] sections /stuff/toolchains/binutils-2.35/bin/riscv64-linux-gnu-ld: final link failed: bad value But that's far far further on in the build than we were getting before these patches. Even if we end up dealing with the emitted strings a different way [1], I think the first patch here has some value in moving the check to Kconfig so that it's far easier to tell if the toolchain does need/use these extensions from someone's build artifacts. Cheers, Conor. 1 - https://lore.kernel.org/linux-riscv/20230223195112.10489-1-palmer@rivosinc.com/ cc: nathan@kernel.org cc: palmer@dabbelt.com cc: naresh.kamboju@linaro.org cc: linux-riscv@lists.infradead.org cc: llvm@lists.linux.dev Conor Dooley (2): RISC-V: move zicsr/zifencei spec version check to Kconfig RISC-V: make TOOLCHAIN_NEEDS_SPEC_20191213 gas only arch/riscv/Kconfig | 9 +++++++++ arch/riscv/Makefile | 5 +---- 2 files changed, 10 insertions(+), 4 deletions(-) -- 2.39.1
next reply other threads:[~2023-02-23 22:06 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-23 22:05 Conor Dooley [this message] 2023-02-23 22:05 ` [PATCH v1 0/2] RISC-V: avoid build issues for clang/llvm-17 with binutils 2.35 Conor Dooley 2023-02-23 22:05 ` [PATCH v1 1/2] RISC-V: move zicsr/zifencei spec version check to Kconfig Conor Dooley 2023-02-23 22:05 ` Conor Dooley 2023-02-24 16:37 ` Nathan Chancellor 2023-02-24 16:37 ` Nathan Chancellor 2023-02-24 17:00 ` Conor Dooley 2023-02-24 17:00 ` Conor Dooley 2023-03-06 23:52 ` Palmer Dabbelt 2023-03-06 23:52 ` Palmer Dabbelt 2023-03-07 19:14 ` Conor Dooley 2023-03-07 19:14 ` Conor Dooley 2023-03-07 19:24 ` Palmer Dabbelt 2023-03-07 19:24 ` Palmer Dabbelt 2023-02-23 22:05 ` [PATCH v1 2/2] RISC-V: make TOOLCHAIN_NEEDS_SPEC_20191213 gas only Conor Dooley 2023-02-23 22:05 ` Conor Dooley 2023-02-24 16:32 ` Nathan Chancellor 2023-02-24 16:32 ` Nathan Chancellor
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=20230223220546.52879-1-conor@kernel.org \ --to=conor@kernel.org \ --cc=conor.dooley@microchip.com \ --cc=linux-riscv@lists.infradead.org \ --cc=llvm@lists.linux.dev \ --cc=naresh.kamboju@linaro.org \ --cc=nathan@kernel.org \ --cc=palmer@dabbelt.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: linkBe 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.