similar to: [LLVMdev] building gcc with clang/llvm

I see what my problem is here.... I'll continue to move further. Seems like Richards fix is still okay. On 02/25/2014 02:42 PM, Eric Christopher wrote: > On Tue, Feb 25, 2014 at 2:41 PM, reed kotler <rkotler at mips.com> wrote: >> On 02/25/2014 02:38 PM, Eric Christopher wrote: >>> On Tue, Feb 25, 2014 at 2:32 PM, reed kotler <rkotler at mips.com> wrote:

On 02/25/2014 02:38 PM, Eric Christopher wrote: > On Tue, Feb 25, 2014 at 2:32 PM, reed kotler <rkotler at mips.com> wrote: >> On 02/25/2014 09:30 AM, Richard Sandiford wrote: >>> reed kotler <rkotler at mips.com> writes: >>>> On 02/24/2014 04:42 PM, Eric Christopher wrote: >>>>> On Mon, Feb 24, 2014 at 4:40 PM, reed kotler <rkotler at

On 02/24/2014 04:42 PM, Eric Christopher wrote: > On Mon, Feb 24, 2014 at 4:40 PM, reed kotler <rkotler at mips.com> wrote: >> I need to leave soon and will take a look in the morning. >> >> I did look at the autoconf input files configure.ac >> >> There is a disable-zlib but not a disable-valgrind, even though it seems >> like there used to be.

On 02/25/2014 09:30 AM, Richard Sandiford wrote: > reed kotler <rkotler at mips.com> writes: >> On 02/24/2014 04:42 PM, Eric Christopher wrote: >>> On Mon, Feb 24, 2014 at 4:40 PM, reed kotler <rkotler at mips.com> wrote: >>>> I need to leave soon and will take a look in the morning. >>>> >>>> I did look at the autoconf input files

I need to leave soon and will take a look in the morning. I did look at the autoconf input files configure.ac There is a disable-zlib but not a disable-valgrind, even though it seems like there used to be. You can find scripts on the internet when you google of people adding disable-valgrind to configure. I can probably implement disable-valgrind in configure.ac. Reed On 02/24/2014 04:33

On 02/24/2014 04:19 PM, Eric Christopher wrote: > On Mon, Feb 24, 2014 at 4:14 PM, reed kotler <rkotler at mips.com> wrote: >> I'm trying to build a native hosted mips compiler on ubuntu x86. >> >> When I run configure with clang/llvm as the compiler, configure thinks that >> zlib is present and that valgrind is. >> >> But later on the make it

I'm trying to build a native hosted mips compiler on ubuntu x86. When I run configure with clang/llvm as the compiler, configure thinks that zlib is present and that valgrind is. But later on the make it cannot find zlib.h. If I tell it to not do compression, then it does not look for zlib.h but dies looking for valgrind, even if I tell it to disable-valgrind. If I configure using

In case anyone is interested.... We don't need to compile llvm/clang using gcc anymore for the building of mips hosted llvm compilers. We build a linux mips hosted compiler starting with llvm/clang on x86 linux using the normal configure scripts and then can use that resulting compiler to build further llvm/clang native compilers on the mips linux host. The cross compiler and native

We are considering running clang format on the whole Mips target. Is there any rule against this? Is there any good argument against doing this even if there is no rule against it? TIA. Reed

the good news is that (thanks to Simon) the clang driver is working so well for Mips now that we are more or less switching away from using llc during development for all our various host/target configurations. the bad news is that we have make clang all the time and it is really slow to do that. we used to be able to just make in the lib/target/Mips and then in llc and it was really fast.

Hi David, What kind of "a lot of out-of-tree changes"? You should push changes incrementally as you do work. Holding onto changes means that many things, not just reformatting, can make them need to be redone. We frequently clean up and rewrite code to make it cleaner and easier to maintain. We are moving to a more strict internal review and pushing of changes and post commit

On 16 August 2013 20:02, reed kotler <rkotler at mips.com> wrote: > -std=gnu89 is not valid for c++ > I think the point here is that this is the default std for GCC but not Clang, so you have to force clang to behave like GCC. For C++, you'll have to force whatever default GCC has for it's C++ standard. Though, GCC 4.8 is getting very close to Clang's behaviour, so

I used the suite with clang 3.3 a few months ago. If I remember correctly, I ran into the same error seen here: http://lists.cs.uiuc.edu/pipermail/llvmdev/2010-November/036013.html Although it doesn't seem to be a problem with the frontend, adding -std=gnu89, as suggested, fixed everything for me. H. ----- Original Message ----- From: reed kotler Sent: 08/16/13 01:26 AM To: LLVM Developers

I've always debugged the backend llc by running it as a separate executable. I'm seeing a bug that only happens when I run the compiler from clang. How do you debug this from gdb? I can put a breakpoint but it never stops when I say "run ...." Tia. Reed

What is the basic command line for using clang/llvm to produce ppc linux code? Tia. Reed

On 08/16/2013 02:23 PM, David Chisnall wrote: > On 16 Aug 2013, at 22:01, reed kotler <rkotler at mips.com> wrote: > >> we used to be able to just make in the lib/target/Mips and then in llc and it was really fast. >> >> part of it is probably that we have all this debug information that we don't need because none of use are working on clang itself (well, almost

I have a test that will only fail if I run clang and not if I run llc by itself but it's an llc issue. Where would I put such a test? Are there similar tests in the "make check" or "make check-all" suite? Tia. Reed

On 08/16/2013 01:42 PM, Renato Golin wrote: > On 16 August 2013 20:02, reed kotler <rkotler at mips.com > <mailto:rkotler at mips.com>> wrote: > > -std=gnu89 is not valid for c++ > > > I think the point here is that this is the default std for GCC but not > Clang, so you have to force clang to behave like GCC. For C++, you'll > have to force

On 03/19/2015 09:57 AM, David Blaikie wrote: > > > On Thu, Mar 19, 2015 at 9:52 AM, Reed Kotler <reed.kotler at imgtec.com > <mailto:reed.kotler at imgtec.com>> wrote: > > On 03/19/2015 09:38 AM, David Blaikie wrote: >> >> >> On Thu, Mar 19, 2015 at 9:34 AM, Reed Kotler >> <reed.kotler at imgtec.com <mailto:reed.kotler at

On 08/16/2013 02:13 PM, Eli Friedman wrote: > On Fri, Aug 16, 2013 at 2:01 PM, reed kotler <rkotler at mips.com > <mailto:rkotler at mips.com>> wrote: > > the good news is that (thanks to Simon) the clang driver is > working so well for Mips now that we are more or less switching > away from using llc during development for all our various >