llvm dev - Dec 2012 - [LLVMdev] Compile code for arm

OK. Thanks for your help.
My problem is I am playing with the size of registerfile in ARM. I thought
I can do it with only modifying the Target in the LLVM directory. But if it
is going to use gcc-toolchain, then I need to modify them as well which is
a huge work!

Best Regards,
A. Yazdanbakhsh
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
PhD. Student
School of Electrical and Computer Engineering
University of Wisconsin-Madison
E-mail:     yazdanbakhsh at wisc.edu


<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<



On Sat, Dec 8, 2012 at 2:05 PM, Renato Golin <rengolin at
systemcall.org>wrote:
> Ok, These are the three options you should be playing with:
>
> -ccc-host-triple $(CCC_HOST_TRIPLE_ARM) \
> --sysroot=$(SYSROOT_ARM) \
> -gcc-toolchain $(GCC_TOOLCHAIN)
>
> Where the (sic) host triple defines the "target" triple too.
>
> Sysroot and gcc-toolchain is where you'll find the libraries and
> binutils for the ARM targets (you'll need them, since LLVM still
can't
> cross-compile on its own).
>
> Another alternative is to compile to assembly and assembly/link with
> ARM gnu binutils, which is essentially the same thing, for now.
>
> Feel free to search for those three options on the list and you'll
> find a plethora or examples and discussions that will guide you
> through the process.
>
> cheers,
> --renato
>
>
> On 8 December 2012 19:52, Amir Yazdanbakhsh <amir.yazdanbakhsh at
gmail.com>
> wrote:
> > Thanks for your help. But I got this warning which it seems it
doesn't
> use
> > -triple
> >
> > "clang: warning: argument unused during compilation: '-triple
> arm-none-eabi'
> > "
> >
> > Best Regards,
> > A. Yazdanbakhsh
> >
>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >
> > PhD. Student
> > School of Electrical and Computer Engineering
> > University of Wisconsin-Madison
> > E-mail:     yazdanbakhsh at wisc.edu
> >
> >
> >
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
> >
> >
> >
> > On Sat, Dec 8, 2012 at 1:43 PM, Renato Golin <rengolin at
systemcall.org>
> > wrote:
> >>
> >> On 8 December 2012 19:10, Amir Yazdanbakhsh <
> amir.yazdanbakhsh at gmail.com>
> >> wrote:
> >> > Hi,
> >> >
> >> > I've installed clang version 3.3 on ubuntu.
> >> > I want to cross-compile a C code into ARM (preferably) ARMv7.
I want
> to
> >> > get
> >> > both assembly code and binary. Can anyone help me what are
the steps
> >> > which
> >> > should I take?
> >>
> >> clang -triple arm-none-eabi (or many other variations including
> >> 'armv5', 'armv7a', 'linux',
'gnueabi', etc).
> >>
> >> There are other options, like -mcpu, -mfpu, -march, -mthumb that
you
> >> can also tune. I'm not sure there is a list of all available
options,
> >> but since you have the source, you can look into ToolChain.cpp or
> >> Tools.cpp in Clang/lib/Driver and see for yourself all the
available
> >> options.
> >>
> >>
> >> > Second question, Is there anyway to tell compiler not to use
any
> >> > Thumb/NEON/VFP instructions?
> >>
> >> Using the same flags, you can tune at your leisure. The
combination of
> >> compiler flags might not be the most straightforward, as this is
> >> somewhat a messy region. I advise you to search the list and try a
bit
> >> for yourself, always checking on clang's source what's
available.
> >>
> >> cheers,
> >> --renato
> >
> >
>
>
>
> --
> cheers,
> --renato
>
> http://systemcall.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20121208/1098ed07/attachment.html>

Hi Amir,

On Dec 8, 2012 8:13 PM, "Amir Yazdanbakhsh" <amir.yazdanbakhsh at
gmail.com>
wrote:
> My problem is I am playing with the size of registerfile in ARM. I
thought I can do it with only modifying the Target in the LLVM directory.
But if it is going to use gcc-toolchain, then I need to modify them as well
which is a huge work!

That sort of depends how you modify it. If you just want to look at
assembly output by clang then probably nothing in GCC needs modifying. All
compiling to assembly relies on is the headers, which don't really have any
specific information about the number of registers.

If you want to produce valid executables in some sense, then it appears
you've got two options (as well as quite a bit of work on an emulator
anyway):
1. Add the registers using a currently UNDEFINED section of the instruction
space. This way the existing GCC libraries will probably be functional,
though you'll only be testing the efficiency of part of the system being
upgraded.
2. Mangle encodings even more, in which case you will have to rebuild the
libraries. Clang may or may not be capable of doing that.

Regards.

Tim
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20121208/14c88afc/attachment.html>

Thanks Tim.

I just need the assembly file. Anyway, I still have problem with generating
assembly for the ARM without having any thumb and other fancy instructions.

Best Regards,
A. Yazdanbakhsh
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
PhD. Student
School of Electrical and Computer Engineering
University of Wisconsin-Madison
E-mail:     yazdanbakhsh at wisc.edu


<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<



On Sat, Dec 8, 2012 at 3:39 PM, Tim Northover <t.p.northover at
gmail.com>wrote:
> Hi Amir,
>
> On Dec 8, 2012 8:13 PM, "Amir Yazdanbakhsh" <amir.yazdanbakhsh
at gmail.com>
> wrote:
> > My problem is I am playing with the size of registerfile in ARM. I
> thought I can do it with only modifying the Target in the LLVM directory.
> But if it is going to use gcc-toolchain, then I need to modify them as well
> which is a huge work!
>
> That sort of depends how you modify it. If you just want to look at
> assembly output by clang then probably nothing in GCC needs modifying. All
> compiling to assembly relies on is the headers, which don't really have
any
> specific information about the number of registers.
>
> If you want to produce valid executables in some sense, then it appears
> you've got two options (as well as quite a bit of work on an emulator
> anyway):
> 1. Add the registers using a currently UNDEFINED section of the
> instruction space. This way the existing GCC libraries will probably be
> functional, though you'll only be testing the efficiency of part of the
> system being upgraded.
> 2. Mangle encodings even more, in which case you will have to rebuild the
> libraries. Clang may or may not be capable of doing that.
>
> Regards.
>
> Tim
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20121208/2fae9dde/attachment.html>