search for: abi's

...When I start ocfs using /etc/init.d/ocfs start, I receive the following errors: [root@RAC1 root]# /etc/init.d/ocfs start Loading OCFS: /sbin/insmod ocfs node_name=RAC1.localdomain ip_address=192.168.61 2 ip_port=7000 cs=1793 guid=8ABD4778558998D89F6B005056404953 comm_voting=1 /lib/modules/2.4.9-e-ABI/ocfs/ocfs.o: unresolved symbol truncate_inode_pages_Rde 1bef54 /lib/modules/2.4.9-e-ABI/ocfs/ocfs.o: unresolved symbol proc_mkdir_R70e19c74 /lib/modules/2.4.9-e-ABI/ocfs/ocfs.o: unresolved symbol generic_file_aio_read_R3 4ac6074 /lib/modules/2.4.9-e-ABI/ocfs/ocfs.o: unresolved symbol __bforget_Radb...

...m <mailto:zakk0610 at gmail.com>> wrote: > > > David Blaikie <dblaikie at gmail.com <mailto:dblaikie at gmail.com>> 於 2020年1月6日 週一 下午2:23寫道： > If this is something that can vary per file in a compilation and resolve correctly when one object file is built with one ABI and another object file is built with a different ABI (that seems to be antithetical to the concept of "ABI" Though) - then it should be a subtarget feature. > > ABI is generally something that has to be agreed upon across object files - so it wouldn't make sense to link two ob...

Hi all, I'm trying to understand which ABIs are supported in the PowerPC backend and I'm getting a bit confused. Here's what I've gathered so far alongside with some questions. - In PPCSubtarget.h there's DarwinABI, SVR4ABI and ELFv2ABI. - The CodeGenerator documentation claims that the AIX PowerPC ABI is followed (with som...

----- Original Message ----- > From: "Ulrich Weigand" <Ulrich.Weigand at de.ibm.com> > To: "David Wiberg" <dwiberg at gmail.com> > Cc: llvmdev at cs.uiuc.edu > Sent: Wednesday, July 30, 2014 2:29:22 PM > Subject: Re: [LLVMdev] [PowerPC] ABI questions > > Hi David, > > > I'm trying to understand which ABIs are supported in the PowerPC > > backend and I'm getting a bit confused. Here's what I've gathered > > so > > far alongside with some questions. > > Sorry for the confusion, t...

David Blaikie <dblaikie at gmail.com> 於 2020年1月6日 週一 下午2:23寫道： > If this is something that can vary per file in a compilation and resolve > correctly when one object file is built with one ABI and another object > file is built with a different ABI (that seems to be antithetical to the > concept of "ABI" Though) - then it should be a subtarget feature. > > ABI is generally something that has to be agreed upon across object files > - so it wouldn't make sense...

...k0610 at gmail.com>> wrote: >> >> >> David Blaikie <dblaikie at gmail.com <mailto:dblaikie at gmail.com>> 於 2020年1月6日 週一 下午2:23寫道： >> If this is something that can vary per file in a compilation and resolve correctly when one object file is built with one ABI and another object file is built with a different ABI (that seems to be antithetical to the concept of "ABI" Though) - then it should be a subtarget feature. >> >> ABI is generally something that has to be agreed upon across object files - so it wouldn't make sense to lin...

...gt;>>> >>>> >>>> David Blaikie <dblaikie at gmail.com> 於 2020年1月6日 週一 下午2:23寫道： >>>> >>>>> If this is something that can vary per file in a compilation and >>>>> resolve correctly when one object file is built with one ABI and another >>>>> object file is built with a different ABI (that seems to be antithetical to >>>>> the concept of "ABI" Though) - then it should be a subtarget feature. >>>>> >>>>> ABI is generally something that has to be agree...

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 o...

Right. I think that's what we ended up doing rather than a more general attribute on the module itself. *shrugs* Probably ok? I'd probably prefer not to have to have target code to do the evaluation if possible, but everything is weird and an edge case - mips abis more than some :) -eric On Wed, Jan 8, 2020 at 8:58 AM David Blaikie <dblaikie at gmail.com> wrote: > Oh, I should say - the module flags metadata also has support for "error > if you try to merge two modules with different values for this flag". > > On Wed, Jan 8, 2...

I also work on the RISC-V backend, and have been doing a little work on the ELF psABI document for RISC-V. I agree that, conceptually, the psABI choice should be in the module metadata. Zakk, however, has discovered a phase ordering issue within LLVM that relates to this approach. The phase ordering problem is that the LTO backend is currently setup without interrogating the curre...

Hello Ulrich, Thank you for a good explanation of the different variants. 2014-07-30 21:29 GMT+02:00 Ulrich Weigand <Ulrich.Weigand at de.ibm.com>: > Hi David, > >> I'm trying to understand which ABIs are supported in the PowerPC >> backend and I'm getting a bit confused. Here's what I've gathered so >> far alongside with some questions. > > Sorry for the confusion, this all should probably be cleaned up a bit. > In general, LLVM today supports the following ABI...

...quot;unexpected failures". It's fewer failures than I saw on RC1 though. $ clang --version clang version 3.8.0 (http://llvm.org/git/clang.git 6b6df26f3b3b96552353a593bdc93333cf9ea6c3) (http://llvm.org/git/llvm.git 43928f790962f5f6d796416ae8c90b95efeaf01a) Target: armv7l-unknown-linux-gnueabihf Thread model: posix InstalledDir: /opt/clang-latest/bin ... Expected Passes : 22688 Expected Failures : 141 Unsupported Tests : 422 Unexpected Passes : 13 Unexpected Failures: 31 ... ******************** Failing Tests (31): libc++abi :: catch_array_01.pass.cpp libc++abi ::...

...道： > Ah, OK - thanks for walking me through that. > > Fair enough, I think I understand the issue/tradeoff now - and that the > other module level metadata don't currently influence the target > configuration at this level? > > I'm not sure, I only know that the target-abi is decided and computed when instantiating the TargetMachine, and TragetMachine constructor doesn't have IR as argument. I guess this starts to come from the other direction for me, then: what > purpose does the "target triple" in the module textual IR serve? I guess > it's...

On Sun, Nov 22, 2015 at 8:09 AM, Renato Golin <renato.golin at linaro.org> wrote: > On 22 November 2015 at 03:59, Brian Cain <brian.cain at gmail.com> wrote: > > Should I expect the "-openmp" to work for this RC? > > Only if it worked before on the target you're building to in 3.7.0. > Ok, I'll check if I can get it to work on 3.7.0. > >

On Wed, Jun 18, 2014 at 2:03 AM, Matheus Almeida <Matheus.Almeida at imgtec.com> wrote: >> Why Imagination Technologies do not offer the latest MIPS ABI document download link just like the ISA docs? > It's something we're considering to do and the documents should be available at some point in the [hopefully] not too distant future. > >> then why GCC disagree with some MIPS ABI, it should be freely designed by MIPS ABI designer...

...;>> >>> Fair enough, I think I understand the issue/tradeoff now - and that the >>> other module level metadata don't currently influence the target >>> configuration at this level? >>> >>> >> I'm not sure, I only know that the target-abi is decided and computed >> when instantiating the TargetMachine, and TragetMachine constructor doesn't >> have IR as argument. >> > > Could you look into the other module level metadata to understand/explain > that, as it may help inform the design here? > > I g...

On Wed, Mar 27, 2013 at 2:28 PM, Anton Korobeynikov <asl at math.spbu.ru>wrote: > Hi Eric, > > > From my perspective Win32 is the windows ABI and mingw and cygwin are > their own ABIs > No. They are using Windows Platform ABI for almost everything (e.g. > calling API, C runtime, etc.). At least mingw does. The differences > are exactly in unspecified area (e.g. passing / returning structs by > value). > > The only di...

On Mon, Jan 20, 2020 at 8:05 AM Sam Elliott via llvm-dev < llvm-dev at lists.llvm.org> wrote: > To follow up on this issue: > > Our plan is still to encode `target-abi` into the module flags for RISC-V > LLVM IR modules. As was pointed out earlier in this thread, the function > lowering in Clang is slightly different for the ABIs which support hardware > floating point. Therefore adding the `target-abi` metadata at the very > least can help catch plac...

...lt; > llvm-dev at lists.llvm.org> wrote: > >> >> >> On Mon, Jan 20, 2020 at 8:05 AM Sam Elliott via llvm-dev < >> llvm-dev at lists.llvm.org> wrote: >> >>> To follow up on this issue: >>> >>> Our plan is still to encode `target-abi` into the module flags for >>> RISC-V LLVM IR modules. As was pointed out earlier in this thread, the >>> function lowering in Clang is slightly different for the ABIs which support >>> hardware floating point. Therefore adding the `target-abi` metadata at the >>&gt...

Thank you very much for your information and documents! Why Imagination Technologies do not offer the latest MIPS ABI document download link just like the ISA docs? If they thought no much people interested in that doc, they had to make greate effort on compiler like GCC,LLVM by themself,then why GCC disagree with some MIPS ABI, it should be freely designed by MIPS ABI designer and compiler backend target implemen...