> No, it should be marked as "REQUIRES: x86-64-registered-target".
- It would fail also on x86_64-mingw32. "REQUIRES:x86_64" would not make sense then. - I believe it is temporary marking. I know XFAIL might not suitable in clang tests, though. For example XFAIL:arm matches both --host=arm and --target=arm. If anyone found any failure (or xpass), then please disable whole test. ...Takumi 2013/1/25 Joey Gouly <[email protected]>: > No, it should be marked as "REQUIRES: x86-64-registered-target". > > Joey > ________________________________________ > From: [email protected] [[email protected]] On > Behalf Of Renato Golin [[email protected]] > Sent: 25 January 2013 08:36 > To: NAKAMURA Takumi > Cc: cfe-commits > Subject: Re: [cfe-commits] r173361 - in /cfe/trunk: > include/clang/Driver/Compilation.h include/clang/Driver/Util.h > lib/Driver/Compilation.cpp lib/Driver/Driver.cpp lib/Driver/Tools.cpp > lib/Driver/Tools.h test/Driver/output-file-cleanup.c > > On 25 January 2013 06:58, NAKAMURA Takumi > <[email protected]<mailto:[email protected]>> wrote: > For now, I have XFAIL'ed for mingw and ppc, in r173428. > > It's also failing on ARM. Is it the same situation when a back-end is not > compiled and you get a NULL pointer on the target specific parser? If so, we > should mark it as XFAIL all over. > > --renato > > > > -- IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose the > contents to any other person, use it for any purpose, or store or copy the > information in any medium. Thank you. > _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
