<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 01/11/2013 06:53 PM, David Blaikie
wrote:<br>
</div>
<blockquote
cite="mid:CAENS6EtpRjs2RT5-zYOM=4=bZNPbqTrtuAD_eYvjshjqWgNgRQ@mail.gmail.com"
type="cite">
<pre wrap="">On Fri, Jan 11, 2013 at 6:46 PM, reed kotler <a class="moz-txt-link-rfc2396E" href="mailto:rkotler@mips.com"><rkotler@mips.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">In some clang tests, they seem to use something other than filecheck
for example in Sema/address_spaces.c
// RUN: %clang_cc1 %s -fsyntax-only -verify
#define _AS1 __attribute__((address_space(1)))
#define _AS2 __attribute__((address_space(2)))
#define _AS3 __attribute__((address_space(3)))
void bar(_AS2 int a); // expected-error {{parameter may not be qualified
with an address space}}
void foo(_AS3 float *a,
_AS1 float b) // expected-error {{parameter may not be qualified
with an address space}}
Where is this documented?
</pre>
</blockquote>
<pre wrap="">
<a class="moz-txt-link-freetext" href="http://clang.llvm.org/doxygen/classclang_1_1VerifyDiagnosticConsumer.html#details">http://clang.llvm.org/doxygen/classclang_1_1VerifyDiagnosticConsumer.html#details</a>
(though, honestly, I've never read the documentation for it - picked
it up most by reading/examples/experience. It's fairly simple)
</pre>
</blockquote>
Nice. The doc had what I was looking for.<br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<pre class="fragment" style="font-family: Fixed, monospace; font-size: 13px; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; border-top-style: solid; border-right-style: solid; border-bottom-style: solid; border-left-style: solid; border-top-color: rgb(204, 204, 204); border-right-color: rgb(204, 204, 204); border-bottom-color: rgb(204, 204, 204); border-left-color: rgb(204, 204, 204); border-image: initial; background-color: rgb(245, 245, 245); margin-top: 4px; margin-bottom: 4px; margin-left: 2px; margin-right: 8px; padding-left: 6px; padding-right: 6px; padding-top: 4px; padding-bottom: 4px; color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="comment" style="color: rgb(
128, 0, 0); ">expected-no-diagnostics</span></pre>
<br>
Seems like filecheck though is much more powerful. This must be an
earlier method for generating tests.<br>
<br>
But in my case I would need to write two different tests if I didn't
use filecheck.<br>
<br>
I'm just trying to test that<br>
__attribute__(mips16) <br>
<br>
continues to generate a warning if the architecture is not mips and
generates no diagnostic if it is mips.<br>
<br>
<br>
</body>
</html>