Makefile: Don't specify mabi or march
PATCH 1/1 Makefile: Don't specify mabi or march
To avoid
can't link double-float modules with soft-float modules
errors when building 32-bit openSBI don't specify mabi or march.
--- Makefile | 2 -- 1 file changed, 2 deletions(-)
Makefile +0 -2
@@ -196,7 +196,6 @@ GENFLAGS += $(firmware-genflags-y) CFLAGS = -g -Wall -Werror -ffreestanding -nostdlib -fno-strict-aliasing -O2 CFLAGS += -fno-omit-frame-pointer -fno-optimize-sibling-calls CFLAGS += -mno-save-restore -mstrict-align -CFLAGS += -mabi=$(PLATFORM_RISCV_ABI) -march=$(PLATFORM_RISCV_ISA) CFLAGS += -mcmodel=$(PLATFORM_RISCV_CODE_MODEL) CFLAGS += $(GENFLAGS) CFLAGS += $(platform-cflags-y)
@@ -210,7 +209,6 @@ CPPFLAGS += $(firmware-cppflags-y) ASFLAGS = -g -Wall -nostdlib -D__ASSEMBLY__ ASFLAGS += -fno-omit-frame-pointer -fno-optimize-sibling-calls ASFLAGS += -mno-save-restore -mstrict-align -ASFLAGS += -mabi=$(PLATFORM_RISCV_ABI) -march=$(PLATFORM_RISCV_ISA) ASFLAGS += -mcmodel=$(PLATFORM_RISCV_CODE_MODEL) ASFLAGS += $(GENFLAGS) ASFLAGS += $(platform-asflags-y)
Signature · 1 line
2.28.0
PATCH 1/1 Makefile: Don't specify mabi or march
Quoted 4 lines · Alistair Francis
To avoid
can't link double-float modules with soft-float modules
errors when building 32-bit openSBI don't specify mabi or march.
What happens if you want to build for a different ABI or ISA string deliberately? Especially with something like Clang where every compiler is a cross-compiler. Users should be able to specify an ABI or ISA string if they want and have it honoured, either via PLATFORM_RISCV_ABI/ISA or by using += for CFLAGS everywhere rather than overwriting it entirely (which is the more standard thing to do for software that isn't RISC-V-specific).
Jess
Quoted 33 lines
Signed-off-by Alistair Francis <[email protected]>---
Makefile| 2 --1 file changed, 2 deletions(-)Makefile +0
-0@@ -196,7 +196,6 @@ GENFLAGS += $(firmware-genflags-y)CFLAGS = -g -Wall -Werror -ffreestanding -nostdlib -fno-strict-aliasing -O2
CFLAGS += -fno-omit-frame-pointer -fno-optimize-sibling-calls
CFLAGS += -mno-save-restore -mstrict-align
-CFLAGS += -mabi=$(PLATFORM_RISCV_ABI) -march=$(PLATFORM_RISCV_ISA)
CFLAGS += -mcmodel=$(PLATFORM_RISCV_CODE_MODEL)
CFLAGS += $(GENFLAGS)
CFLAGS += $(platform-cflags-y)Makefile +0
-0@@ -210,7 +209,6 @@ CPPFLAGS += $(firmware-cppflags-y)ASFLAGS = -g -Wall -nostdlib -D__ASSEMBLY__
ASFLAGS += -fno-omit-frame-pointer -fno-optimize-sibling-calls
ASFLAGS += -mno-save-restore -mstrict-align
-ASFLAGS += -mabi=$(PLATFORM_RISCV_ABI) -march=$(PLATFORM_RISCV_ISA)
ASFLAGS += -mcmodel=$(PLATFORM_RISCV_CODE_MODEL)
ASFLAGS += $(GENFLAGS)
ASFLAGS += $(platform-asflags-y)Signature · 7 lines
2.28.0 -- opensbi mailing list opensbi at lists.infradead.org http://lists.infradead.org/mailman/listinfo/opensbi
PATCH 1/1 Makefile: Don't specify mabi or march
Quoted 6 lines · Jessica Clarke
Quoted 3 lines · Alistair Francis
To avoid
can't link double-float modules with soft-float modules
errors when building 32-bit openSBI don't specify mabi or march.
Quoted 9 lines
What happens if you want to build for a different ABI or ISA string deliberately? Especially with something like Clang where every compiler
is a cross-compiler. Users should be able to specify an ABI or ISA string if they want and have it honoured, either via PLATFORM_RISCV_ABI/ISA or by using += for CFLAGS everywhere rather than
overwriting it entirely (which is the more standard thing to do for software that isn't RISC-V-specific).
A user could do that by specifying their own CFLAGS when building to allow them to specify a ISA or ABI.
Currently no platform set PLATFORM_RISCV_ABI as it defaults to ilp32 or lp64.
No platform also sets PLATFORM_RISCV_ISA which is always rv32/64imafdc.
Alistair
Quoted 41 lines
Jess
Quoted 38 lines
Signed-off-by Alistair Francis <[email protected]>---
Makefile| 2 --1 file changed, 2 deletions(-)Makefile +0
-0@@ -196,7 +196,6 @@ GENFLAGS += $(firmware-genflags-y)CFLAGS = -g -Wall -Werror -ffreestanding -nostdlib
-fno-strict-aliasing -O2
CFLAGS += -fno-omit-frame-pointer -fno-optimize-
sibling-calls
CFLAGS += -mno-save-restore -mstrict-alignMakefile +0
-2-CFLAGS += -mabi=$(PLATFORM_RISCV_ABI) -march=$(PLATFORM_RISCV_ISA)CFLAGS += -mcmodel=$(PLATFORM_RISCV_CODE_MODEL)
CFLAGS += $(GENFLAGS)
CFLAGS += $(platform-cflags-y)Makefile +0
-0@@ -210,7 +209,6 @@ CPPFLAGS += $(firmware-cppflags-y)ASFLAGS = -g -Wall -nostdlib -D__ASSEMBLY__
ASFLAGS += -fno-omit-frame-pointer -fno-optimize-
sibling-calls
ASFLAGS += -mno-save-restore -mstrict-alignMakefile +0
-2-ASFLAGS += -mabi=$(PLATFORM_RISCV_ABI) -march=$(PLATFORM_RISCV_ISA)ASFLAGS += -mcmodel=$(PLATFORM_RISCV_CODE_MODEL)
ASFLAGS += $(GENFLAGS)
ASFLAGS += $(platform-asflags-y)Signature · 7 lines
2.28.0 -- opensbi mailing list opensbi at lists.infradead.org http://lists.infradead.org/mailman/listinfo/opensbi
PATCH 1/1 Makefile: Don't specify mabi or march
Quoted 18 lines · Alistair Francis
Quoted 6 lines · Jessica Clarke
Quoted 3 lines · Alistair Francis
To avoid
can't link double-float modules with soft-float modules
errors when building 32-bit openSBI don't specify mabi or march.Quoted 9 lines
What happens if you want to build for a different ABI or ISA string deliberately? Especially with something like Clang where every compiler
is a cross-compiler. Users should be able to specify an ABI or ISA string if they want and have it honoured, either via PLATFORM_RISCV_ABI/ISA or by using += for CFLAGS everywhere rather than
overwriting it entirely (which is the more standard thing to do for software that isn't RISC-V-specific).
Quoted 2 lines
A user could do that by specifying their own CFLAGS when building to allow them to specify a ISA or ABI.
Makefile:196:CFLAGS = -g -Wall -Werror -ffreestanding -nostdlib -fno-strict-aliasing -O2
That doesn't work so well with user-supplied CFLAGS.
Quoted 2 lines
Currently no platform set
PLATFORM_RISCV_ABIas it defaults to ilp32 or lp64.
We do. We have new ABIs for our extension (see cheri-cpu.org).
Quoted 1 line
No platform also sets
PLATFORM_RISCV_ISAwhich is always rv32/64imafdc.
We do.
Jess
Quoted 38 lines
Quoted 38 lines
Quoted 38 lines
Signed-off-by Alistair Francis <[email protected]>---
Makefile| 2 --1 file changed, 2 deletions(-)Makefile +0
-0@@ -196,7 +196,6 @@ GENFLAGS += $(firmware-genflags-y)CFLAGS = -g -Wall -Werror -ffreestanding -nostdlib
-fno-strict-aliasing -O2
CFLAGS += -fno-omit-frame-pointer -fno-optimize-
sibling-calls
CFLAGS += -mno-save-restore -mstrict-alignMakefile +0
-2-CFLAGS += -mabi=$(PLATFORM_RISCV_ABI) -march=$(PLATFORM_RISCV_ISA)CFLAGS += -mcmodel=$(PLATFORM_RISCV_CODE_MODEL)
CFLAGS += $(GENFLAGS)
CFLAGS += $(platform-cflags-y)Makefile +0
-0@@ -210,7 +209,6 @@ CPPFLAGS += $(firmware-cppflags-y)ASFLAGS = -g -Wall -nostdlib -D__ASSEMBLY__
ASFLAGS += -fno-omit-frame-pointer -fno-optimize-
sibling-calls
ASFLAGS += -mno-save-restore -mstrict-alignMakefile +0
-2-ASFLAGS += -mabi=$(PLATFORM_RISCV_ABI) -march=$(PLATFORM_RISCV_ISA)ASFLAGS += -mcmodel=$(PLATFORM_RISCV_CODE_MODEL)
ASFLAGS += $(GENFLAGS)
ASFLAGS += $(platform-asflags-y)Signature · 7 lines
2.28.0 -- opensbi mailing list opensbi at lists.infradead.org http://lists.infradead.org/mailman/listinfo/opensbi
PATCH 1/1 Makefile: Don't specify mabi or march
Quoted 25 lines · Jessica Clarke
Quoted 23 lines · Alistair Francis
Quoted 21 lines · Jessica Clarke
Quoted 4 lines · Alistair Francis
To avoid
can't link double-float modules with soft-float modules
errors when building 32-bit openSBI don't specify mabi or march.What happens if you want to build for a different ABI or ISA string
deliberately? Especially with something like Clang where every compiler
is a cross-compiler. Users should be able to specify an ABI or ISA
string if they want and have it honoured, either via PLATFORM_RISCV_ABI/ISA or by using += for CFLAGS everywhere rather
than
overwriting it entirely (which is the more standard thing to do for
software that isn't RISC-V-specific).
Quoted 6 lines
Quoted 3 lines
A user could do that by specifying their own CFLAGS when building to
allow them to specify a ISA or ABI.Makefile:196:CFLAGS = -g -Wall -Werror -ffreestanding
-nostdlib -fno-strict-aliasing -O2
Ah, I didn't realise this. I'll change it to a +=
Quoted 8 lines
That doesn't work so well with user-supplied CFLAGS.
Quoted 3 lines
Currently no platform set
PLATFORM_RISCV_ABIas it defaults to ilp32 or
lp64.We do. We have new ABIs for our extension (see cheri-cpu.org).
Ah ok. Maybe it's worth upstreamign the cheri implementaiton then?
Alistair
Quoted 47 lines
Quoted 3 lines
No platform also sets
PLATFORM_RISCV_ISAwhich is always rv32/64imafdc.We do.
Jess
Quoted 39 lines
Quoted 39 lines
Quoted 39 lines
Signed-off-by Alistair Francis <[email protected]>---
Makefile| 2 --1 file changed, 2 deletions(-)Makefile +0
-0@@ -196,7 +196,6 @@ GENFLAGS += $(firmware-genflags-y)CFLAGS = -g -Wall -Werror -ffreestanding
Makefile +0
-2-nostdlib -fno-strict-aliasing -O2CFLAGS += -fno-omit-frame-pointer -fno-optimize-
sibling-calls
CFLAGS += -mno-save-restore -mstrict-alignMakefile +0
-2-CFLAGS += -mabi=$(PLATFORM_RISCV_ABI) -march=$(PLATFORM_RISCV_ISA)CFLAGS += -mcmodel=$(PLATFORM_RISCV_CODE_MODEL)
CFLAGS += $(GENFLAGS)
CFLAGS += $(platform-cflags-y)Makefile +0
-0@@ -210,7 +209,6 @@ CPPFLAGS += $(firmware-cppflags-y)ASFLAGS = -g -Wall -nostdlib -D__ASSEMBLY__
ASFLAGS += -fno-omit-frame-pointer -fno-optimize-
sibling-calls
ASFLAGS += -mno-save-restore -mstrict-alignMakefile +0
-2-ASFLAGS += -mabi=$(PLATFORM_RISCV_ABI) -march=$(PLATFORM_RISCV_ISA)ASFLAGS += -mcmodel=$(PLATFORM_RISCV_CODE_MODEL)
ASFLAGS += $(GENFLAGS)
ASFLAGS += $(platform-asflags-y)Signature · 7 lines
2.28.0 -- opensbi mailing list opensbi at lists.infradead.org http://lists.infradead.org/mailman/listinfo/opensbi
PATCH 1/1 Makefile: Don't specify mabi or march
Quoted 26 lines · Alistair Francis
Quoted 25 lines · Jessica Clarke
Quoted 23 lines · Alistair Francis
Quoted 21 lines · Jessica Clarke
Quoted 4 lines · Alistair Francis
To avoid
can't link double-float modules with soft-float modules
errors when building 32-bit openSBI don't specify mabi or march.What happens if you want to build for a different ABI or ISA string
deliberately? Especially with something like Clang where every compiler
is a cross-compiler. Users should be able to specify an ABI or ISA
string if they want and have it honoured, either via PLATFORM_RISCV_ABI/ISA or by using += for CFLAGS everywhere rather
than
overwriting it entirely (which is the more standard thing to do for
software that isn't RISC-V-specific).
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines
A user could do that by specifying their own CFLAGS when building to
allow them to specify a ISA or ABI.Makefile:196:CFLAGS = -g -Wall -Werror -ffreestanding
-nostdlib -fno-strict-aliasing -O2Ah, I didn't realise this. I'll change it to a +=
Thanks. Same goes for AFLAGS, and I didn't check LDFLAGS etc.
Quoted 9 lines
Quoted 7 lines
That doesn't work so well with user-supplied CFLAGS.
Quoted 3 lines
Currently no platform set
PLATFORM_RISCV_ABIas it defaults to ilp32 or
lp64.We do. We have new ABIs for our extension (see cheri-cpu.org).
Ah ok. Maybe it's worth upstreamign the cheri implementaiton then?
We never really finished it properly and have been stuck on BBL. Well, in theory it works, but it just hasn't seen the same amount of testing as it's not in day-to-day use. I don't think it makes much sense to upstream the very CHERI-specific bits (instructions, configuration, etc) since it's ultimately a research architecture for now and we do want to be able to make breaking changes, but there may well be things we can upstream that make our fork's diff smaller (the nature of the architecture and software model means that we routinely find integer/pointer confusion in projects and can upstream many of our diffs as simple code quality improvements to use the right type). I do know it required substantially less hacking than BBL though to get something that booted, especially in the build system.
Jess
PATCH 1/1 Makefile: Don't specify mabi or march
Quoted 51 lines · Jessica Clarke
Quoted 35 lines · Alistair Francis
Quoted 34 lines · Jessica Clarke
Quoted 30 lines · Alistair Francis
Quoted 8 lines · Jessica Clarke
Quoted 4 lines · Alistair Francis
To avoid
can't link double-float modules with soft-float modules
errors when building 32-bit openSBI don't specify mabi or march.Quoted 16 lines
What happens if you want to build for a different ABI or ISA string
deliberately? Especially with something like Clang where every
compiler
is a cross-compiler. Users should be able to specify an ABI or
ISA
string if they want and have it honoured, either via PLATFORM_RISCV_ABI/ISA or by using += for CFLAGS everywhere rather
than
overwriting it entirely (which is the more standard thing to do
for
software that isn't RISC-V-specific).A user could do that by specifying their own CFLAGS when building
to
allow them to specify a ISA or ABI.Quoted 5 lines
Review
Quoted 3 lines
Makefile:196:CFLAGS = -g -Wall -Werror
(quoted diff) +0
-2-ffreestanding -nostdlib -fno-strict-aliasing -O2Ah, I didn't realise this. I'll change it to a +=
Thanks. Same goes for AFLAGS, and I didn't check LDFLAGS etc.
Quoted 6 lines
Quoted 6 lines
That doesn't work so well with user-supplied CFLAGS.
Quoted 3 lines
Currently no platform set
PLATFORM_RISCV_ABIas it defaults to ilp32 or
lp64.
Quoted 5 lines
Quoted 3 lines
Quoted 1 line
We do. We have new ABIs for our extension (see cheri-cpu.org).
Ah ok. Maybe it's worth upstreamign the cheri implementaiton then?
We never really finished it properly and have been stuck on BBL.
That is annoying.
Quoted 7 lines
Well,
in theory it works, but it just hasn't seen the same amount of testing
as it's not in day-to-day use. I don't think it makes much sense to upstream the very CHERI-specific bits (instructions, configuration, etc) since it's ultimately a research architecture for now and we do want to be able to make breaking changes, but there may well be
Agreed, but I'm sure at least some of it could be upstreamed. That helps us at least build test other platforms.
Quoted 5 lines
things
we can upstream that make our fork's diff smaller (the nature of the architecture and software model means that we routinely find integer/pointer confusion in projects and can upstream many of our diffs as simple code quality improvements to use the right type). I
That would be great!
Quoted 3 lines
do
know it required substantially less hacking than BBL though to get something that booted, especially in the build system.
I'm glad to hear that :)
Alistair
Quoted 3 lines
Jess
PATCH 1/1 Makefile: Don't specify mabi or march
In reply to Alistair FrancisQuoted 5 lines · Alistair Francis
Quoted 2 lines · Jessica Clarke
Makefile:196:CFLAGS = -g -Wall -Werror -ffreestanding
-nostdlib -fno-strict-aliasing -O2Ah, I didn't realise this. I'll change it to a +=
That won't work with `make CFLAGS=foo'.
Andreas.
Signature · 3 lines
Andreas Schwab, schwab at linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
PATCH 1/1 Makefile: Don't specify mabi or march
In reply to Alistair FrancisQuoted 4 lines · Alistair Francis
To avoid
can't link double-float modules with soft-float modules
errors when building 32-bit openSBI don't specify mabi or march.
We have a lot of users (including me) who use multilib toolchain to compile OpenSBI for desired mabi and march. In fact, I have one common toolchain for ilp32, ilp32d, lp64, and lp64d.
By removing "-mabi" and "-march", we are enforcing users to depend on default mabi and march of toolchain. This means we can't use multilib toolchain for OpenSBI.
I would suggest to add a separate makefile option (e.g. PLATFORM_USE_TOOLCHAIN_MABI, PLATFORM_USE_TOOLCHAIN_MARCH) which when enabled will skip specifying "-mabi" and "-march" in various compiler/assembler/linker flags.
Regards,
Anup
Quoted 34 lines
Signed-off-by Alistair Francis <[email protected]>--- Makefile | 2 -- 1 file changed, 2 deletions(-)Makefile +0
-3@@ -196,7 +196,6 @@ GENFLAGS += $(firmware-genflags-y) CFLAGS = -g -Wall -Werror -ffreestanding -nostdlib -fno-strict-aliasing -O2 CFLAGS += -fno-omit-frame-pointer -fno-optimize-sibling-calls CFLAGS += -mno-save-restore -mstrict-align -CFLAGS += -mabi=$(PLATFORM_RISCV_ABI) -march=$(PLATFORM_RISCV_ISA) CFLAGS += -mcmodel=$(PLATFORM_RISCV_CODE_MODEL) CFLAGS += $(GENFLAGS) CFLAGS += $(platform-cflags-y)@@ -210,7 +209,6 @@ CPPFLAGS += $(firmware-cppflags-y) ASFLAGS = -g -Wall -nostdlib -D__ASSEMBLY__ ASFLAGS += -fno-omit-frame-pointer -fno-optimize-sibling-calls ASFLAGS += -mno-save-restore -mstrict-align -ASFLAGS += -mabi=$(PLATFORM_RISCV_ABI) -march=$(PLATFORM_RISCV_ISA) ASFLAGS += -mcmodel=$(PLATFORM_RISCV_CODE_MODEL) ASFLAGS += $(GENFLAGS) ASFLAGS += $(platform-asflags-y) --2.28.0
--
opensbi mailing list
opensbi at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi
PATCH 1/1 Makefile: Don't specify mabi or march
Quoted 12 lines · Anup Patel
Quoted 4 lines · Alistair Francis
To avoid
can't link double-float modules with soft-float modules
errors when building 32-bit openSBI don't specify mabi or march.We have a lot of users (including me) who use multilib toolchain to compile OpenSBI for desired mabi and march. In fact, I have one common toolchain for ilp32, ilp32d, lp64, and lp64d.
Quoted 8 lines
By removing "-mabi" and "-march", we are enforcing users to depend on default mabi and march of toolchain. This means we can't use multilib toolchain for OpenSBI.
I would suggest to add a separate makefile option (e.g.
PLATFORM_USE_TOOLCHAIN_MABI,PLATFORM_USE_TOOLCHAIN_MARCH) which when enabled will skip specifying "-mabi" and "-march" in various compiler/assembler/linker flags.
Here's a change which will work for your case as well as with multilib toolchains:
Makefile +0 -0
@@ -94,6 +94,8 @@ DTC = dtc # Guess the compillers xlen OPENSBI_CC_XLEN := $(shell TMP=`$(CC) -dumpmachine | sed
's/riscv\([0-9][0-9]\).*/\1/'; echo $${TMP}) +OPENSBI_CC_ABI := $(shell TMP=$(CC) -v 2>&1 | sed -n 's/.*\(with\-abi=\([a-zA-Z0-9]*\)\).*/\2/p'; echo $${TMP}) +OPENSBI_CC_ISA := $(shell TMP=$(CC) -v 2>&1 | sed -n 's/.*\(with\-arch=\([a-zA-Z0-9]*\)\).*/\2/p'`; echo $${TMP})
# Setup platform XLEN
ifndef PLATFORM_RISCV_XLEN
@@ -143,14 +145,22 @@ deps-y+=$(firmware-objs-path-y:.o=.dep)
# Setup platform ABI, ISA and Code Model ifndef PLATFORM_RISCV_ABI
- ifeq ($(PLATFORM_RISCV_XLEN), 32)
- PLATFORM_RISCV_ABI = ilp$(PLATFORM_RISCV_XLEN)
+ ifndef PLATFORM_USE_TOOLCHAIN_ABI
+ ifeq ($(PLATFORM_RISCV_XLEN), 32)
+ PLATFORM_RISCV_ABI = ilp$(PLATFORM_RISCV_XLEN)
+ else
+ PLATFORM_RISCV_ABI = lp$(PLATFORM_RISCV_XLEN)
+ endif
else
- PLATFORM_RISCV_ABI = lp$(PLATFORM_RISCV_XLEN)
+ PLATFORM_RISCV_ABI = $(OPENSBI_CC_ABI)
endif
endif
ifndef PLATFORM_RISCV_ISA
- PLATFORM_RISCV_ISA = rv$(PLATFORM_RISCV_XLEN)imafdc
+ ifndef PLATFORM_USE_TOOLCHAIN_ISA
+ PLATFORM_RISCV_ISA = rv$(PLATFORM_RISCV_XLEN)imafdc
+ else
+ PLATFORM_RISCV_ISA = $(OPENSBI_CC_ISA)
+ endif
endif
ifndef PLATFORM_RISCV_CODE_MODEL
PLATFORM_RISCV_CODE_MODEL = medany
Regards,
Anup
Quoted 38 lines
Regards,
AnupQuoted 34 lines
Signed-off-by Alistair Francis <[email protected]>--- Makefile | 2 -- 1 file changed, 2 deletions(-)Makefile +0
-3@@ -196,7 +196,6 @@ GENFLAGS += $(firmware-genflags-y) CFLAGS = -g -Wall -Werror -ffreestanding -nostdlib -fno-strict-aliasing -O2 CFLAGS += -fno-omit-frame-pointer -fno-optimize-sibling-calls CFLAGS += -mno-save-restore -mstrict-align -CFLAGS += -mabi=$(PLATFORM_RISCV_ABI) -march=$(PLATFORM_RISCV_ISA) CFLAGS += -mcmodel=$(PLATFORM_RISCV_CODE_MODEL) CFLAGS += $(GENFLAGS) CFLAGS += $(platform-cflags-y)@@ -210,7 +209,6 @@ CPPFLAGS += $(firmware-cppflags-y) ASFLAGS = -g -Wall -nostdlib -D__ASSEMBLY__ ASFLAGS += -fno-omit-frame-pointer -fno-optimize-sibling-calls ASFLAGS += -mno-save-restore -mstrict-align -ASFLAGS += -mabi=$(PLATFORM_RISCV_ABI) -march=$(PLATFORM_RISCV_ISA) ASFLAGS += -mcmodel=$(PLATFORM_RISCV_CODE_MODEL) ASFLAGS += $(GENFLAGS) ASFLAGS += $(platform-asflags-y) --2.28.0
--
opensbi mailing list
opensbi at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi
PATCH 1/1 Makefile: Don't specify mabi or march
In reply to Alistair FrancisQuoted 3 lines · Alistair Francis
To avoid
can't link double-float modules with soft-float modules
errors when building 32-bit openSBI don't specify mabi or march.
What version of binutils are you using?
Andreas.
Signature · 3 lines
Andreas Schwab, schwab at linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
PATCH 1/1 Makefile: Don't specify mabi or march
Quoted 7 lines · Andreas Schwab
Quoted 3 lines · Alistair Francis
To avoid
can't link double-float modules with soft-float modules
errors when building 32-bit openSBI don't specify mabi or march.What version of binutils are you using?
I'm using 2.35.
Alistair
Quoted 3 lines
Andreas.