Searched refs:bad (Results 51 - 66 of 66) sorted by relevance

123

/barrelfish-master/lib/openssl-1.0.0d/crypto/threads/
H A Dmttest.c224 if (--argc < 1) goto bad;
229 if (--argc < 1) goto bad;
234 if (--argc < 1) goto bad;
239 if (--argc < 1) goto bad;
244 if (--argc < 1) goto bad;
252 if (--argc < 1) goto bad;
267 bad:
/barrelfish-master/lib/lwip2/src/netif/ppp/
H A Dchap_ms.c262 goto bad;
268 goto bad;
290 bad:
309 goto bad; /* not even the right length */
346 bad:
/barrelfish-master/include/lwip2/netif/ppp/
H A Dchap_ms.c262 goto bad;
268 goto bad;
290 bad:
309 goto bad; /* not even the right length */
346 bad:
/barrelfish-master/lib/openssl-1.0.0d/crypto/evp/
H A Dencode.c418 int i,num=0,bad=0; local
/barrelfish-master/lib/libc/net/
H A Dgetaddrinfo.c346 /* external reference: error, and label bad */ \
348 goto bad; \
512 goto bad;
543 goto bad;
616 goto bad;
661 bad:
1115 * XXX: hardcoded scope type values are bad...
1324 bad:
/barrelfish-master/usr/eclipseclp/Kernel/lib/
H A Dprofile.pl167 search(0, Preds, pred(_, I, _, _)) % add to bad samples
H A Dforall.pl136 % collect args in list (bad example, use =.. if you really want to do that!)
/barrelfish-master/doc/015-disk-driver-arch/
H A Dfat.tex6 of the next cell, and special values indicate unused, bad and list-terminating
/barrelfish-master/usr/skb/programs/
H A Dobjects3.pl233 % assert/retract are really bad in terms of performance
/barrelfish-master/include/vm/
H A Dvm_page.c243 vm_paddr_t bad; local
272 bad = strtoq(pos, &cp, 0);
274 if (bad == 0) {
286 return (trunc_page(bad));
985 ("vm_page_putfake: bad page %p", m));
1000 ("vm_page_updatefake: bad page %p", m));
/barrelfish-master/doc/023-coreboot/
H A Dcoreboot.tex260 the KCB stop to execute is generally a bad idea as there may be messages waiting
/barrelfish-master/lib/openssl-1.0.0d/util/
H A Dpod2man.pl194 =item bad option in paragraph %d of %s: ``%s'' should be [%s]<%s>
753 warn "$0: bad option in paragraph $. of $ARGV: ``$1'' should be [LCI]<$1>\n";
758 warn "$0: bad option in paragraph $. of $ARGV: ``$1'' should be [CB]<$1>\n";
/barrelfish-master/usr/eclipseclp/documents/intro_paper/
H A Declipse.tex2151 may later turn out to have been bad.
2157 out to be bad, guessing that $X < 50$.
2195 constraint is only a guess, and if it turns out to be a bad guess then
2336 If bad heuristics are chosen the search may methodically explore some
/barrelfish-master/usr/eclipseclp/documents/applications/
H A Dtutorial.tex1474 In this chapter we will discuss input and output with the ECLiPSe system. We will first discuss how to read data into an ECLiPSe program, then discuss different output methods. From this we extract some rules about good and bad data formats that may be useful when defining a data exchange format between different applications. At the end we show how to use a simple report generator library in RiskWise, which converts data lists into HTML reports.
1686 \section{Good and bad data formats}
1687 When defining the data format for an input or output file, we should choose a representation which suits the ECLiPSe application. Table \ref{InputFormats} shows good and bad formats\index{data format}. Prolog terms are very easy to read and to write, simple tabular forms are easy to write, but more complex to read. Comma separated files need a special tokenizer which separates fields by comma characters. The most complex input format is given by a fixed column format\index{fixed column format}\index{format, fixed column}, for example generated by FORTRAN\index{FORTRAN} applications. We should avoid such data formats as input if possible, since they require significant development effort.
1698 \caption{\label{InputFormats}Good and bad input formats}
/barrelfish-master/doc/003-hake/
H A DHake.tex137 programming language built in, one ends up implementing a bad one
/barrelfish-master/usr/eclipseclp/documents/userman/
H A Dumscompiler.tex972 backtracking due to bad indexing.

Completed in 287 milliseconds

123