search for: pr14109

...t into the LLVM build system so that you can do in-tree builds of compiler-rt for all the targets you can target with your new clang. I will gate this functionality on a flag just like the work above so it won't break existing users. This re-working will also provide a more robust solution for PR14109. PR14109 can't be properly fixed without making compiler-rt an external project because CMake doesn't really support changing the compiler after you've already configured a directory. Some of this functionality already exists in clang/runtime, but we'll want to transition to that b...

...LLVM build system so that you can do in-tree builds of compiler-rt for all the targets you can target with your new clang. I will gate this functionality on a flag just like the work above so it won't break existing users. > > This re-working will also provide a more robust solution for PR14109. PR14109 can't be properly fixed without making compiler-rt an external project because CMake doesn't really support changing the compiler after you've already configured a directory. > > Some of this functionality already exists in clang/runtime, but we'll want to transition...

...ild system so that you can do in-tree builds of compiler-rt for all the targets you can target with your new clang. I will gate this functionality on a flag just like the work above so it won't break existing users. >> >> This re-working will also provide a more robust solution for PR14109. PR14109 can't be properly fixed without making compiler-rt an external project because CMake doesn't really support changing the compiler after you've already configured a directory. >> >> Some of this functionality already exists in clang/runtime, but we'll want to tr...

...stem so that you can do in-tree > builds of compiler-rt for all the targets you can target with your new > clang. I will gate this functionality on a flag just like the work above so > it won't break existing users. > > This re-working will also provide a more robust solution for PR14109. > PR14109 can't be properly fixed without making compiler-rt an external > project because CMake doesn't really support changing the compiler after > you've already configured a directory. > > Some of this functionality already exists in clang/runtime, but we'll want...

...stem so that you can do in-tree > builds of compiler-rt for all the targets you can target with your new > clang. I will gate this functionality on a flag just like the work above so > it won't break existing users. > > This re-working will also provide a more robust solution for PR14109. > PR14109 can't be properly fixed without making compiler-rt an external > project because CMake doesn't really support changing the compiler after > you've already configured a directory. > > Some of this functionality already exists in clang/runtime, but we'll want...

...LLVM build system so that you can do in-tree builds of compiler-rt for all the targets you can target with your new clang. I will gate this functionality on a flag just like the work above so it won't break existing users. > > This re-working will also provide a more robust solution for PR14109. PR14109 can't be properly fixed without making compiler-rt an external project because CMake doesn't really support changing the compiler after you've already configured a directory. > > Some of this functionality already exists in clang/runtime, but we'll want to transition...

...so that you can do in-tree builds of compiler-rt for all the targets you can target with your new clang. I will gate this functionality on a flag just like the work above so it won't break existing users. > >> > >> This re-working will also provide a more robust solution for PR14109. PR14109 can't be properly fixed without making compiler-rt an external project because CMake doesn't really support changing the compiler after you've already configured a directory. > >> > >> Some of this functionality already exists in clang/runtime, but we'll...

...do in-tree >> builds of compiler-rt for all the targets you can target with your new >> clang. I will gate this functionality on a flag just like the work above so >> it won't break existing users. >> >> This re-working will also provide a more robust solution for PR14109. >> PR14109 can't be properly fixed without making compiler-rt an external >> project because CMake doesn't really support changing the compiler after >> you've already configured a directory. >> >> Some of this functionality already exists in clang/runtime...

...at you can do in-tree builds of compiler-rt for all the targets you can target with your new clang. I will gate this functionality on a flag just like the work above so it won't break existing users. >>>> >>>> This re-working will also provide a more robust solution for PR14109. PR14109 can't be properly fixed without making compiler-rt an external project because CMake doesn't really support changing the compiler after you've already configured a directory. >>>> >>>> Some of this functionality already exists in clang/runtime, but we...

...t into the LLVM build system so that you can do in-tree builds of compiler-rt for all the targets you can target with your new clang. I will gate this functionality on a flag just like the work above so it won't break existing users. This re-working will also provide a more robust solution for PR14109. PR14109 can't be properly fixed without making compiler-rt an external project because CMake doesn't really support changing the compiler after you've already configured a directory. Some of this functionality already exists in clang/runtime, but we'll want to transition to that b...

Le 23 mai 2013 à 11:52, Óscar Fuentes <ofv at wanadoo.es> a écrit : > Renato Golin <renato.golin at linaro.org> writes: > >> I currently use CMake+Ninja on native builds on both x86 and ARM without >> problems, but I agree that cross-compilation is not yet mastered. > > What's wrong with cross-compilation? > At least

Renato Golin <renato.golin at linaro.org> writes: > I currently use CMake+Ninja on native builds on both x86 and ARM without > problems, but I agree that cross-compilation is not yet mastered. What's wrong with cross-compilation?

On 11 March 2015 at 04:14, Chandler Carruth <chandlerc at google.com> wrote: > Just to rebase things a bit, here is some context. > > - This is a 60+ email thread spreading across a month of time. > - I've not read every single email and I don't think it makes sense to > assume the context of the first email applies to the most recent. I think we all agree that