search for: mzbqvys5qwjvpeaetuwhcq

...__________________________ > > LLVM Developers mailing list > > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > > > > > > > To report this email as spam click > https://www.mailcontrol.com/sr/MZbqvYs5QwJvpeaetUwhCQ== . Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom More information can be found at www.csr.com. Keep up to date with CSR on...

...t; > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > > > > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > > > > > > > > > > > > > > > > > To report this email as spam click > > > https://www.mailcontrol.com/sr/MZbqvYs5QwJvpeaetUwhCQ== . > > > > > > > > Member of the CSR plc group of companies. CSR plc registered in > > England and Wales, registered number 4187346, registered office > > Churchill House, Cambridge Business Park, Cowley Road, Cambridge, > > CB4 0WZ, United Kingdom More in...

...ke a misleading diff... that SubArchType stuff was reverted >> recently in trunk. >> > I recall that patch going across. There's just no reason for it in the > diff from Matthew. > > -eric > > > To report this email as spam click https://www.mailcontrol.com/sr/MZbqvYs5QwJvpeaetUwhCQ== . Hi people, I apologise for the earlier bad diff. Here's one I've just generated against the latest svn. The TOT sources build fine with these additions. Is there any reason now why this patch cannot be submitted on my behalf? My concern is that I cannot submit further work for our c...

...http://llvm.cs.uiuc.edu > > > > > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > > > > > > > > > > > > > > > > > > > > > > To report this email as spam click > > > > https://www.mailcontrol.com/sr/MZbqvYs5QwJvpeaetUwhCQ== . > > > > > > > > > > > > Member of the CSR plc group of companies. CSR plc registered in > > > England and Wales, registered number 4187346, registered office > > > Churchill House, Cambridge Business Park, Cowley Road, Cambridge, > > &...

How does LLVM generate machine code for different architectures? For example, the machine code for x86 and amd will vary. How does LLVM convert its IR to machine code for different architectures.Can you please explain the approach? Is it just write two different programs for two different architectures and pass a flag to the compiler based on which machine code you want to generate? Thanks a lot

On 7/9/14, 12:33 PM, Eric Christopher wrote: > Any reason why you deleted code that isn't related? > > -eric > >> - enum SubArchType { >> - NoSubArch, >> - >> - ARMSubArch_v8, >> - ARMSubArch_v7, >> - ARMSubArch_v7em, >> - ARMSubArch_v7m, >> - ARMSubArch_v7s, >> - ARMSubArch_v6, >> -

> There are no dumb questions. My answer might seem a bit disappointing though > :-) I just scrolled quickly though the log. The errors appear in red, they > were easy to spot. Depending on the build system used, you can also search > for specific patterns (like *** for make) in the log. Specifically, it's the "stdio" link under the red failing step in this case.

I'm working on lldb. I've just submitted a very small change (r217229) to Triple.h/.cpp. Soon after I get a mail subject: buildbot failure in LLVM on lld-x86_64-darwin13 Details: http://lab.llvm.org:8011/builders/lld-x86_64-darwin13/builds/2571 Blamelist: mg11 My small change certainly did not cause lldb's build to fail on my machine. I looked into the build-log: