search for: secify

...opinion seemed to be keep simple FileCheck tests but that tests should be run with a specific triple; however that triple shouldn't always be x86_64 (because that's a bit special). There've been about 5-10 tests where the test was testing something that was architecture specific without secifying they needed it (eg, testing for specific x86_64 machine optimizations without doing that); again the upshot has been to have these requirements specified explicitly. There have been 5-10 JIT code tests where "support" code pasted from, eg, lli into a test hadn't been updated when t...

...ders (I guess thats the problem?). I heard that Shoutcast servers do not support the x-audiocast format anyway. Yet Icecast is said to be 100% Shoutcast compatible. I also tried adding relays with the "relay pull" command directly in the console and used the -i option and the -m option to secify a local mountpoint. However when connecting with a client to that mountpoint Icecast didn't seem to find the mountpoint at all (according to the debug output), although my relay was indeed in the list you get via "relay list". Sometimes adding or just listing relays with the "rel...

I'm ok with this in principle, but how about with the nuance that some tests (eg test/codegen) explicitly opt into march=native? -Chris On Nov 30, 2012, at 12:16 PM, Daniel Dunbar <daniel at zuster.org> wrote: > Hi all, > > We consistently see test failures arising because by default many of our tests run in a mode where the tool (clang or llc) pick host-dependent behavior.

On Fri, Nov 30, 2012 at 8:04 PM, Chris Lattner <clattner at apple.com> wrote: > I'm ok with this in principle, but how about with the nuance that some > tests (eg test/codegen) explicitly opt into march=native? > I'd really like the default behavior to be something that forces the test to either be independent of the targeted triple, or explicitly set a target. I like the