similar to: [LLVMdev] How can I using the right triple?

> > > The word 'all' is what still bothers me here. If any one piece of the information is derived from incorrect information in the triple, then the behaviour will likely be incorrect. > > > > If it's possible to be derived from the triple then it's going to be correct or the triple is incorrect. > > If it's something that's overridden later

Rewrote the ABI example in terms of clang -cc1as which is a supported tool. Note that the same problems exist and that they are unrelated to the existence of TargetMachine or not since TargetMachine gets the relevant information from the Triple it holds. This information is incorrect, even as a starting point. Please do read the other examples in my previous email. It contains a number of

> > Note that the same problems exist and that they are unrelated to the existence > > of TargetMachine or not since TargetMachine gets the relevant information from > > the Triple it holds. This information is incorrect, even as a starting point. > > I believe we're going to disagree here as the TargetMachine does not get all of its > information from the Triple -

Eric Christopher echristo at gmail.com<mailto:echristo at gmail.com> writes: > The lack of a TargetMachine at the MC level was something I brought up a long time ago in this thread > with my proposed solutions. This is what needs to be fixed, especially given that targets can switch ISA, > ABI, floating point, etc within a single assemble action. I’ve been watching this thread in

Hi LLVM developers, I am implementing Loong Language[1] using Clang FrontEnd and LLVM MiddleEnd. I add `wire`[2] Builtin Type, and clang is able to parse very small testcase fulladder[3] but failed to work for 10+K loc RISCV E203 project[4]: Loongson clang version 7.0.0 (git at github.com:Loong-Language/loong-clang.git 8f7e826f27abbe12ea08d9563490298c38d3adc1) (git at

Hi Eric, It's the unsolved problems on the pass-MCTargetOptions-everywhere path that are my main concern with that approach rather than the amount of work. The first problem is that the result of IRObjectFile::CollectAsmUndefinedRefs() depends on the ABI but IRObjectFile doesn't know it. How would you deliver the ABI to IRObjectFile? The second problem is that IRLinker will link

On Mon, Sep 26, 2011 at 1:23 AM, Anton Korobeynikov <anton at korobeynikov.info> wrote: > Hello > >> How can I use the right triple? >> Thanks. > You're using the "right" triplet. However: > 1. Your system is unknown to driver (as shown in the warning) I'm looking into it. > 2. You need to "teach" driver to look for paths to the includes

Hi all, I met this error(title) when i was trying to compile llvm-gcc-4.2-2.7 on loongson2f,a mips compatible platform.I also failed to build a cross-compiler and the error message was the same . Is that means llvm-gcc cannot support mips back-end now? Thanks. Here is my configure options: $export TARGET=mips64el-unknown-linux-gnu $../../src/llvm-gcc-4.2-2.7.source/configure

> > The word 'all' is what still bothers me here. If any one piece of the information is derived from incorrect information in the triple, then the behaviour will likely be incorrect. > > If it's possible to be derived from the triple then it's going to be correct or the triple is incorrect. > If it's something that's overridden later because it can't be

On 10 September 2010 04:47, Liu <proljc at gmail.com> wrote: > trying this: > clang -march=armv7-a -mcpu=cortex-a9 -ccc-host-triple > arm-none-linux -ccc-gcc-name arm-none-linux-gnueabi-gcc a.c Hi Liu, That doesn't work for me. $ clang -march=armv7-a -mcpu=cortex-a9 -ccc-host-triple arm-none-linux -ccc-gcc-name arm-none-linux-gnueabi-gcc alias.c clang: warning: unknown

Hello > How can I use the right triple? > Thanks. You're using the "right" triplet. However: 1. Your system is unknown to driver (as shown in the warning) 2. You need to "teach" driver to look for paths to the includes for your platform -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

I have somebody working on this. You can communicate with him. He just started and does not have his mips account yet. /simon/@/atanasyan/.com There are many issues related to the driver. Reed On 09/25/2011 07:36 PM, Liu wrote: > On Mon, Sep 26, 2011 at 1:23 AM, Anton Korobeynikov > <anton at korobeynikov.info> wrote: >> Hello >> >>> How can I use the right

1. I would like to know why there is a difference in function prologue generated for same function with clang and gcc. Compiler options used for gcc were as follows: arm-linux-gnueabi-gcc all-types.c -w -march=armv7-a -mtune=cortex-a8 -mfloat-abi=softfp -mfpu=vfp -g -lm -o all-types_gcc Compiler options used for clang were as follows: /usr/local/bin/clang all-types.c -w

On Tue, Sep 27, 2011 at 1:23 AM, reed kotler <rkotler at mips.com> wrote: > I have somebody working on this. > > You can communicate with him. He just started and does not have his mips > account yet. > simon at atanasyan.com > > There are many issues related to the driver. > > Reed You mean he is working on clang driver or llvm be? --Liu > > > On

On Wed, Jul 18, 2012 at 3:52 PM, Renato Golin <rengolin at systemcall.org> wrote: > On 18 July 2012 14:33, salvatore benedetto > <salvatore.benedetto at gmail.com> wrote: >> but I still haven't figure out how to build for cortex-m3 >> >> clang -march=armv7-m -mfloat-abi=soft <something missing?> testReference.cpp -c > > -march should have done

> > I assume with target you mean the backend? Consider the x86 backend. It > supports 32bit and 64bit mode, with the GNU x32 ABI in between. There > are three different executable formats support (ELF, PE, MachO) with > different constraints. Some platforms require 32bit alignment of the > stack, others require 128bit alignment. The list goes on. The triple > specifies >

> OK, I'm going to just reply to the last because I think it's the most important part of all this and would like to try to have us side tracked again. If you'd like I can reply to it, but let's take the last part first :) > > > > Could you please provide some examples of things that are impossible right now > > > with command lines, how those interact with

On Jul 7, 2010, at 12:22 AM, 吴伟 wrote: > Hi all, > I met this error(title) when i was trying to compile llvm-gcc-4.2-2.7 on loongson2f,a mips compatible platform.I also failed to build a cross-compiler and the error message was the same . Is that means llvm-gcc cannot support mips back-end now? I don't think that LLVM supports mips64 yet... Bruno? -Chris > Thanks. >

Hi, I am getting the following error from LLVM 2.9/Final for the sparc code and I wonder whether I am misusing the command line options, which are shown below; clang -ccc-host-triple sparc-unknown-linux -ccc-clang-archs sparc -S -emit-llvm sample1.c -o sample1.ll --> clang: warning: unknow platform, assuming -mfloat-abi=soft --> error: error reading 'soft'

Hi, Having recently enabled IAS by default for the MIPS O32 ABI, I'm now trying to do the same thing for the MIPS N64 ABI. Unfortunately, it is not currently possible to enable IAS by default for the N64 ABI without also enabling it for the N32 ABI because this information is not reflected in the triple and that's the only information MipsMCAsmInfo has. This would be fine if it N32 was