search for: d20992

On 9 June 2016 at 18:49, Justin Bogner via llvm-dev <llvm-dev at lists.llvm.org> wrote: > This all seems pretty sensible. Should we also use the opportunity to > split compiler-rt's builtins and profiling/sanitizer/etc runtimes, since > we'll be moving things around anyway? Also be good to make Compiler-RT and libc++ cross-compile for multiple targets... :/ While that may

On 9 June 2016 at 19:13, Chris Bieneman <beanz at apple.com> wrote: >> On 9 June 2016 at 18:49, Justin Bogner via llvm-dev >> <llvm-dev at lists.llvm.org> wrote: >>> This all seems pretty sensible. Should we also use the opportunity to >>> split compiler-rt's builtins and profiling/sanitizer/etc runtimes, since >>> we'll be moving things

...ce for projects that fall into category 1. I don’t think there is any technical reason to drop an in-tree project into projects over tools today, and I think we migrating people who are doing that away from it should be easy. Second I want to add a “runtimes” directory to LLVM to cover case 2 (see D20992). The idea behind this is to use common code in LLVM to support building runtimes. This will allow the full LLVM toolchain to be visible during configuration. I will abstract this functionality into an installed CMake module so that Clang can use it for out-of-tree clang builds. Lastly we need to...

I probably should have stated this in my last email. I see all three of these initiatives as separate restructuring changes. None of them should need to be tied to each other or block the others. > On Jun 10, 2016, at 11:23 AM, Chandler Carruth <chandlerc at gmail.com> wrote: > > On Fri, Jun 10, 2016 at 10:52 AM Chris Bieneman via llvm-dev <llvm-dev at lists.llvm.org

...at fall into category 1. I don’t think there is any technical reason to drop an in-tree project into projects over tools today, and I think we migrating people who are doing that away from it should be easy. >> >> Second I want to add a “runtimes” directory to LLVM to cover case 2 (see D20992). The idea behind this is to use common code in LLVM to support building runtimes. This will allow the full LLVM toolchain to be visible during configuration. I will abstract this functionality into an installed CMake module so that Clang can use it for out-of-tree clang builds. >> >>...

On 14 June 2016 at 17:40, Chris Bieneman <beanz at apple.com> wrote: > The problem comes from that fact that generally builds are structured as configure -> build. What we actually need is "configure some" -> "build some" -> "configure some more" -> "build some more" -> repeat until done. Well, GCC has been doing this for years, and

...egory 1. I don’t think there is any technical reason to drop an in-tree project into projects over tools today, and I think we migrating people who are doing that away from it should be easy. >>>> >>>> Second I want to add a “runtimes” directory to LLVM to cover case 2 (see D20992). The idea behind this is to use common code in LLVM to support building runtimes. This will allow the full LLVM toolchain to be visible during configuration. I will abstract this functionality into an installed CMake module so that Clang can use it for out-of-tree clang builds. >>>> &...

On 12 June 2016 at 00:35, Sean Silva via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> I think the fundamental distinction needs to be following dependency >> graphs because if we don’t get rid of the circular dependency in >> bootstrapping there is no reason to make any changes. > > +1 for what Chandler said here. > > I don't think CMake itself per se

Hi LLVM-Dev, Over the past week or so I’ve been working on build system improvements around the LLVM runtimes directory. You may remember this from the LLVM-Dev discussion (http://lists.llvm.org/pipermail/llvm-dev/2016-June/100859.html), or the patch review discussion (https://reviews.llvm.org/D20992) back in June. Recently, I’ve made a handful of new changes that actually make it useful, and I wanted to blast out this update and encourage people to give it a try. Let me start with an update on the current state. First and foremost, this is not currently supported with multi-configuration ge...

Hi all, I recently bought a Intel D2500HN motherboard with Intel GMA 3600 video card. I want to install FreeBSD 9-Release on it via PXE, but after booting the system, it seems that video card driver doesn't work properly. Have a look at this picture: http://img703.imageshack.us/img703/5648/20120714393.jpg I've tried the # vidcontrol 80x25 but unfortunately it doesn't help. Do

...xd0000000-0xffdfffff] available for PCI devices > [ 0.000000] Booting paravirtualized kernel on bare hardware > [ 0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:8 > nr_node_ids:1 > [ 0.000000] PERCPU: Embedded 27 pages/cpu @ffff88022ec00000 s81408 > r8192 d20992 u262144 > [ 0.000000] pcpu-alloc: s81408 r8192 d20992 u262144 alloc=1*2097152 > [ 0.000000] pcpu-alloc: [0] 0 1 2 3 4 5 6 7 > [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. > Total pages: 2060136 > [ 0.000000] Policy zone: Normal > [ 0.000000] Ke...

...0.000000] e820: [mem 0xd0000000-0xffdfffff] available for PCI devices [ 0.000000] Booting paravirtualized kernel on bare hardware [ 0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:8 nr_node_ids:1 [ 0.000000] PERCPU: Embedded 27 pages/cpu @ffff88022ec00000 s81408 r8192 d20992 u262144 [ 0.000000] pcpu-alloc: s81408 r8192 d20992 u262144 alloc=1*2097152 [ 0.000000] pcpu-alloc: [0] 0 1 2 3 4 5 6 7 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 2060136 [ 0.000000] Policy zone: Normal [ 0.000000] Kernel command line: BOOT_IMAGE=...

Include logs from the failed boot On Jun 11, 2015 10:55 PM, "Andre Campos Rodovalho" < andre.rodovalho at gmail.com> wrote: > Hello, I'm facing issues with a Point of View GT210/218 and nouveau > drivers. I'm using ubuntu server with LXDE on top of it... > > *lshw -c video* output: > *-display > description: VGA compatible controller >

...0.000000] e820: [mem 0xbfa00000-0xfed1bfff] available for PCI devices [ 0.000000] Booting paravirtualized kernel on bare hardware [ 0.000000] setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:4 nr_node_ids:1 [ 0.000000] PERCPU: Embedded 28 pages/cpu @ffff88023fa00000 s85504 r8192 d20992 u524288 [ 0.000000] pcpu-alloc: s85504 r8192 d20992 u524288 alloc=1*2097152 [ 0.000000] pcpu-alloc: [0] 0 1 2 3 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 2046259 [ 0.000000] Policy zone: Normal [ 0.000000] Kernel command line: initrd=latest/ini...