search for: d71387

...codegen so the problem is how to pass ABI info >> into LTO code generator. >> >> The easier way is pass -target-abi via option to LTO codegen, but there >> is linking issue when linking two bitcodes generated by different -mabi >> option. (see https://reviews.llvm.org/D71387#1792169) >> >> Usually the ABI info for a file is derived from target triple, mcpu or >> -mabi, but in RISC-V, target-abi is only derived from -mabi and -mattr >> option, so the one of solutions is encoding target-abi in IR via LLVM >> module flags metadata. >> &...

Hi all. There are two steps in LTO codegen so the problem is how to pass ABI info into LTO code generator. The easier way is pass -target-abi via option to LTO codegen, but there is linking issue when linking two bitcodes generated by different -mabi option. (see https://reviews.llvm.org/D71387#1792169) Usually the ABI info for a file is derived from target triple, mcpu or -mabi, but in RISC-V, target-abi is only derived from -mabi and -mattr option, so the one of solutions is encoding target-abi in IR via LLVM module flags metadata. But there is an another issue in assembler. In curren...

...> There are two steps in LTO codegen so the problem is how to pass ABI info into LTO code generator. > > The easier way is pass -target-abi via option to LTO codegen, but there is linking issue when linking two bitcodes generated by different -mabi option. (see https://reviews.llvm.org/D71387#1792169 <https://reviews.llvm.org/D71387#1792169>) > > Usually the ABI info for a file is derived from target triple, mcpu or -mabi, but in RISC-V, target-abi is only derived from -mabi and -mattr option, so the one of solutions is encoding target-abi in IR via LLVM module flags metada...

...here are two steps in LTO codegen so the problem is how to pass ABI info into LTO code generator. >> >> The easier way is pass -target-abi via option to LTO codegen, but there is linking issue when linking two bitcodes generated by different -mabi option. (see https://reviews.llvm.org/D71387#1792169 <https://reviews.llvm.org/D71387#1792169>) >> >> Usually the ABI info for a file is derived from target triple, mcpu or -mabi, but in RISC-V, target-abi is only derived from -mabi and -mattr option, so the one of solutions is encoding target-abi in IR via LLVM module flag...

...O code generator. >>>>>> >>>>>> The easier way is pass -target-abi via option to LTO codegen, but >>>>>> there is linking issue when linking two bitcodes generated by different >>>>>> -mabi option. (see https://reviews.llvm.org/D71387#1792169) >>>>>> >>>>>> Usually the ABI info for a file is derived from target triple, mcpu >>>>>> or -mabi, but in RISC-V, target-abi is only derived from -mabi and -mattr >>>>>> option, so the one of solutions is encoding targ...

...t;>>>> >>>>>>>> The easier way is pass -target-abi via option to LTO codegen, but >>>>>>>> there is linking issue when linking two bitcodes generated by different >>>>>>>> -mabi option. (see https://reviews.llvm.org/D71387#1792169) >>>>>>>> >>>>>>>> Usually the ABI info for a file is derived from target triple, mcpu >>>>>>>> or -mabi, but in RISC-V, target-abi is only derived from -mabi and -mattr >>>>>>>> option, so the o...

...two steps in LTO codegen so the problem is how to pass ABI info into LTO code generator. >>> >>> The easier way is pass -target-abi via option to LTO codegen, but there is linking issue when linking two bitcodes generated by different -mabi option. (see https://reviews.llvm.org/D71387#1792169) >>> >>> Usually the ABI info for a file is derived from target triple, mcpu or -mabi, but in RISC-V, target-abi is only derived from -mabi and -mattr option, so the one of solutions is encoding target-abi in IR via LLVM module flags metadata. >>> >>> B...

...how to pass ABI >> info into LTO code generator. >> >>> >> >>> The easier way is pass -target-abi via option to LTO codegen, but >> there is linking issue when linking two bitcodes generated by different >> -mabi option. (see https://reviews.llvm.org/D71387#1792169) >> >>> >> >>> Usually the ABI info for a file is derived from target triple, mcpu >> or -mabi, but in RISC-V, target-abi is only derived from -mabi and -mattr >> option, so the one of solutions is encoding target-abi in IR via LLVM >> module...

...nto LTO code generator. >>>> >>> >>>> >>> The easier way is pass -target-abi via option to LTO codegen, but >>>> there is linking issue when linking two bitcodes generated by different >>>> -mabi option. (see https://reviews.llvm.org/D71387#1792169) >>>> >>> >>>> >>> Usually the ABI info for a file is derived from target triple, mcpu >>>> or -mabi, but in RISC-V, target-abi is only derived from -mabi and -mattr >>>> option, so the one of solutions is encoding target-abi...

...problem is how to pass ABI > info into LTO code generator. > > >>> > > >>> The easier way is pass -target-abi via option to LTO codegen, but > there is linking issue when linking two bitcodes generated by different > -mabi option. (see https://reviews.llvm.org/D71387#1792169) > > >>> > > >>> Usually the ABI info for a file is derived from target triple, mcpu > or -mabi, but in RISC-V, target-abi is only derived from -mabi and -mattr > option, so the one of solutions is encoding target-abi in IR via LLVM > module flags meta...

...info into LTO code generator. >>> > >>> >>> > >>> The easier way is pass -target-abi via option to LTO codegen, but >>> there is linking issue when linking two bitcodes generated by different >>> -mabi option. (see https://reviews.llvm.org/D71387#1792169) >>> > >>> >>> > >>> Usually the ABI info for a file is derived from target triple, >>> mcpu or -mabi, but in RISC-V, target-abi is only derived from -mabi and >>> -mattr option, so the one of solutions is encoding target-abi in IR...