similar to: [LLVMdev] Target Triple list

On Mon, Jul 26, 2010 at 12:04 PM, Aaron Gray <aaronngray.lists at gmail.com> wrote: > You probably want to add Cygwin and MinGW32 Triples as well :- >    case Triple::Win32: > +  case Triple::Cygwin: > +  case Triple::MinGW32: >      return new WindowsX86AsmBackend (T); > Aaron Can someone test this on those platforms? That change would effect quite a few people. -

On 26 July 2010 18:08, Michael Spencer <bigcheesegs at gmail.com> wrote: > On Mon, Jul 26, 2010 at 12:04 PM, Aaron Gray <aaronngray.lists at gmail.com> > wrote: > > You probably want to add Cygwin and MinGW32 Triples as well :- > > case Triple::Win32: > > + case Triple::Cygwin: > > + case Triple::MinGW32: > > return new

On 26 July 2010 04:35, Michael Spencer <bigcheesegs at gmail.com> wrote: > Attached is the 5th and final patch of the beginning of COFF support > for MC. It simply makes the X86 backend use it on Win32 targets and > tests it. > > You probably want to add Cygwin and MinGW32 Triples as well :- case Triple::Win32: + case Triple::Cygwin: + case Triple::MinGW32: return

Hello List, I've got a basic question about the target triple. "The TRIPLE record (code 2) contains a variable number of values representing the bytes of the target triple specification string." The statement above is written on BitCodeFormat.html. And from this statement, I became to wonder what specification defines such and such target triple strings. I believe several of the

> Hi Aaron, > > Aaron Gray <aaronngray.lists <at> googlemail.com> writes: > >> unrecognized option '--enable-runtime-pseudo-relocs' > > Interesting. > Does libCompilerDriver.dll link w/o '--enable-runtime-pseudo-relocs'? I have not tried as of yet. > If I understand correctly, this bug makes it impossible to produce > loadable >

Hi Mikhail, > Aaron Gray <aaronngray.lists <at> googlemail.com> writes: >> I have not tried as of yet. > > Just compile with `make VERBOSE=1` and then copy, paste & edit > the offending line. Okay >> I don't think Cygwin supports loadable modules anyway. > > Really, Cygwin doesn't allow to produce DLLs? Then I guess I > should make this a

On Thu, Jul 16, 2009 at 10:04 AM, Aaron Gray<aaronngray.lists at googlemail.com> wrote: > 2009/7/16 Chris Lattner <clattner at apple.com> >> Whats Daniels approach, does he have any online documentation or code, do >> you have an email address so I may talk to him. >> >> Take a look at how asmprinters work >> in include/llvm/Target/TargetRegistry.h .

2009/7/16 Daniel Dunbar <daniel at zuster.org> > On Thu, Jul 16, 2009 at 10:04 AM, Aaron > Gray<aaronngray.lists at googlemail.com> wrote: > > 2009/7/16 Chris Lattner <clattner at apple.com> > >> Whats Daniels approach, does he have any online documentation or code, > do > >> you have an email address so I may talk to him. > >> >

On Thu, Jul 16, 2009 at 11:43 AM, Aaron Gray<aaronngray.lists at googlemail.com> wrote: > 2009/7/16 Daniel Dunbar <daniel at zuster.org> >> >> On Thu, Jul 16, 2009 at 10:04 AM, Aaron >> Gray<aaronngray.lists at googlemail.com> wrote: >> > 2009/7/16 Chris Lattner <clattner at apple.com> >> >> Whats Daniels approach, does he have any

Hi all, There's been some controversies in the TargetTriple changes and I want to explain it better in the list (to a wider audience) and also propose my plans on how to support the ARM platform better, especially cross-compilation in Clang. All this discussion came as a spin-off of bug 8911 (http://llvm.org/bugs/show_bug.cgi?id=8957)... Today we have three major problems in cross-compiling

Hi César, > I changed Module::setTargetTriple to return true/false when an > invalid/valid triple is passed as parameter. target triples with unknown vendor and other fields occur all the time. That's fine as long as you don't need those fields. What I am saying is that a boolean value "valid" or "not valid" isn't very useful in my opinion. Ciao, Duncan.

On Feb 23, 2009, at 10:30 AMPST, Aaron Gray wrote: > On Mon, Feb 23, 2009 at 6:22 PM, Aaron Gray <aaronngray.lists at googlemail.com > > wrote: > On Mon, Feb 23, 2009 at 6:09 PM, Dale Johannesen <dalej at apple.com> > wrote: > These benchmarks are not distributed with llvm (which doesn't have the > legal right to distribute Spec, for example). If you have

I am now getting an X86ATTAsmPrinter error in compiling libstdc++-v3 right near the end of compiling llvm-gcc in valarray-inst.cc. assertion "IndexReg.getReg() != X86::ESP && "X86 doesn't allow scaling by ESP" Does this build on Linux ? My remote Linux box has died and not a ble to reset it for a day or two. /home/ang/build/llvm-gcc/./gcc/xgcc -shared-libgcc

> On Thu, Jul 2, 2009 at 11:46 AM, Aaron > Gray<aaronngray.lists at googlemail.com> wrote: >> Jon, >> >> LLVM seems to be now dependant by default on OCAML and ocamldoc. Can you >> please change this so OCAML is only built and enabled when an >> '--enable-ocaml' flag is set on 'configure'. As I cannot do 'make >> install'

This looks like pr4572. Evan On Jul 27, 2009, at 3:25 AM, Aaron Gray wrote: > I am now getting an X86ATTAsmPrinter error in compiling libstdc++-v3 > right near the end of compiling llvm-gcc in valarray-inst.cc. > > assertion "IndexReg.getReg() != X86::ESP && "X86 doesn't allow > scaling by ESP" > > Does this build on Linux ? > > My

Dale Johannesen wrote: > On Feb 23, 2009, at 10:30 AMPST, Aaron Gray wrote: > > On Mon, Feb 23, 2009 at 6:22 PM, Aaron Gray <aaronngray.lists at googlemail.com<mailto:aaronngray.lists at googlemail.com>> wrote: > On Mon, Feb 23, 2009 at 6:09 PM, Dale Johannesen <dalej at apple.com<mailto:dalej at apple.com>> wrote: > These benchmarks are not distributed with

Hi Renato, > 1. Some ARM triples "arm*-none-eabi" don't get properly recognized, > so Clang doesn't generate correct AAPCS (soft and hard) calls and > don't pass the correct triple to LLC. in order to have "eabi" be properly recognized by LLVM, it is enough to add "eabi" as a valid environment value. Then Triple::Normalize will automatically

Hi Aaron, Aaron Gray <aaronngray.lists <at> googlemail.com> writes: > I have not tried as of yet. Just compile with `make VERBOSE=1` and then copy, paste & edit the offending line. > I don't think Cygwin supports loadable modules anyway. Really, Cygwin doesn't allow to produce DLLs? Then I guess I should make this a configure option.

2009/8/28 Aaron Gray <aaronngray.lists at googlemail.com> > 2009/8/28 Anton Korobeynikov <anton at korobeynikov.info> > >> Hello, Aaron >> >> > -c /home/ang/svn/llvm-gcc-coff/gcc/libgcc2.c -o libgcc/./_popcountsi2.o >> > assertion "V == V2 && "Didn't find key?"" failed: file >> >

Aaron Gray wrote: > On Sun, Mar 1, 2009 at 4:24 AM, Nick Lewycky <nicholas at mxc.ca > <mailto:nicholas at mxc.ca>> wrote: > > Please try this patch. I tried to copy exactly what libtool would do > on Cygwin by reading the libtool source. > > > Hi Nick, > > Working fine on Cygwin :) Great to hear! I've committed the fix in r65922.