search for: 131463

...ier than next week. > > Anyway, JIT failures happens somewhere between 131458 (which is OK) and > 131466 (where JIT tests fail). Let me know if this is enough or I shall > continue to point to the culprit revision directly. Given that revision range, the only remotely likely culprit is 131463. Which basically means that it "broke" because the default target features changed. I'll going to try and debug this. -Eli

On 07/ 4/11 01:39 AM, Eli Friedman wrote: > For the JIT failures, it would be nice if you could track down the SVN > revision when it started failing. (We have an ARM buildbot at > http://google1.osuosl.org:8011/builders/clang-native-arm-cortex-a9 , > but the JIT was already broken when it was set up.) I've used my i.MX53 board to get this, but I'm returning it today back to

On 07/ 8/11 05:26 PM, Eli Friedman wrote: > Given that revision range, the only remotely likely culprit is 131463. > Which basically means that it "broke" because the default target > features changed. And you are right here. 131463 == 131464 which is buggy. 131462 is OK. Thanks, Karel

On Fri, Jul 8, 2011 at 9:30 AM, Karel Gardas <karel.gardas at centrum.cz> wrote: > On 07/ 8/11 05:26 PM, Eli Friedman wrote: >> >> Given that revision range, the only remotely likely culprit is 131463. >>  Which basically means that it "broke" because the default target >> features changed. > > And you are right here. 131463 == 131464 which is buggy. 131462 is OK. Mmm... and I just realized I really can't help track this down because the code paths in question ar...

...k this down because > the code paths in question are probably Linux-specific. I spent a I add the following line back to lib/Support/Unix/Host.inc, Arch = "arm"; And examples/HowToUseJIT works fine. Regards, chenwj [1] http://llvm.org/viewvc/llvm-project?view=rev&revision=131463 -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of Information Science, Academia Sinica, Taiwan (R.O.C.) Tel:886-2-2788-3799 #1667

Hi, all It seems that rev. 131463 [1] makes LLVM failed to recognize ARM correctly. My best guess is the variable LLVM_HOSTTRIPLE got something like "armv7l-unknown-linux-gnueabi" when LLVM compiled natively on ARM. Then the Arch (armv7l) is not recognized by LLVM. As you can see from attach (llvm-131463-gcc-4.4.1-nati...

...OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at lists.freedesktop.org Reporter: pachoramos1 at gmail.com QA Contact: nouveau at lists.freedesktop.org Created attachment 131463 --> https://bugs.freedesktop.org/attachment.cgi?id=131463&action=edit dmesg I see this error in dmesg output: nouveau 0000:01:00.0: DRM: failed to create kernel channel, -22 This message is shown between this: [ 0.990005] VGA switcheroo: detected Optimus DSM method \_SB_.PCI0.PEG0.PEG...