Searched refs:big (Results 1 - 25 of 28) sorted by relevance

12

/barrelfish-master/usr/tests/msun/
H A Dfmaxmin_test.c65 testall_r(long double big, long double small) argument
69 long double expected_max = isnan(big) ? small : big;
70 long double expected_min = isnan(small) ? big : small;
73 TEST(fmaxf, float, big, small, expected_max);
74 TEST(fmaxf, float, small, big, expected_max);
75 TEST(fmax, double, big, small, expected_max);
76 TEST(fmax, double, small, big, expected_max);
77 TEST(fmaxl, long double, big, small, expected_max);
78 TEST(fmaxl, long double, small, big, expected_ma
95 testall(int testnum, long double big, long double small) argument
[all...]
/barrelfish-master/lib/compiler-rt/test/arm/
H A Dcall_apsr.h18 #error big endian support not implemented
/barrelfish-master/usr/skb/programs/
H A Dplat_VE_A15x4_A7x4.pl10 % Statically-initialised hardware facts for the big.LITTLE Fixed Virtual
/barrelfish-master/lib/libc/stdlib/
H A Dmerge.c120 int big, iflag; local
146 i = big = 0;
167 if (!big) { /* here i = 0 */
170 big = 1;
185 big = 0;
/barrelfish-master/lib/gdtoa/
H A Dgethex.c48 int big, esign, havedig, irv, j, k, n, n0, nbits, up, zret; local
125 big = esign = 0;
143 big = 1;
155 if (big) {
/barrelfish-master/lib/compiler-rt/builtins/arm/
H A Daeabi_cdcmp.S12 #error big endian support not implemented
H A Daeabi_cfcmp.S12 #error big endian support not implemented
/barrelfish-master/lib/openssl-1.0.0d/test/
H A Dtests.com184 "starting big number library test, could take a while..."
H A DMakefile225 @echo starting big number library test, could take a while...
/barrelfish-master/usr/eclipseclp/Kernel/lib/
H A Dpretty_print.pl61 % First try to print the term using write/2, if it is too big,
H A Dqueens.pl52 It can be seen that for small N the difference is not very big,
/barrelfish-master/include/sys/
H A Dcapsicum.h338 bool cap_rights_contains(const cap_rights_t *big, const cap_rights_t *little);
/barrelfish-master/tools/fof/
H A DFutureWork.tex8 big pointy teeth.}{Monty Python}
/barrelfish-master/lib/openssl-1.0.0d/crypto/rc4/asm/
H A Drc4-ia64.pl185 # big software-pipelined loop. It MUST be greater-or-equal
583 // big loop.
/barrelfish-master/lib/openssl-1.0.0d/crypto/sha/asm/
H A Dsha512-ia64.pl20 # this one big time). Note that "formally" 924 is about 100 cycles
455 mux1 X[15]=X[15],\@rev };; // eliminated in big-endian
/barrelfish-master/usr/eclipseclp/documents/tutorial/
H A Dhybrid.tex316 To achieve this we introduce sufficiently big multipliers, that when
607 Sending too many constraints to {\tt eplex} can cause a big growth
/barrelfish-master/doc/026-device-queues/
H A Ddevif.tex686 memory chunks, the memory chunks are merged to one big chunk.
751 table entries is limited ($\approx$140000) so registering big amount of memory with
/barrelfish-master/usr/eclipseclp/documents/embedding/
H A Ddbi.tex281 ignored. Otherwise, if the data is too big to fit into the buffer, an error
/barrelfish-master/lib/tommath/
H A Dbn.tex1747 This will store $a$ into the buffer $b$ in big--endian format. Fortunately this is exactly what DER (or is it ASN?)
1754 This will read in an unsigned big--endian array of bytes (octets) from $b$ of length $c$ into $a$. The resulting
/barrelfish-master/doc/014-bulk-transfer/
H A Dbulk-transfer.tex412 available at given time. Ideally, production-pool should be big enough
797 \item Create and add the initial shared-pool big enough to satisfy
/barrelfish-master/usr/eclipseclp/documents/megalog/
H A Ddatabase-sec.tex941 {\bf tmp} and {\bf result}. If these relations are very big, a
/barrelfish-master/lib/pcre/
H A Dpcre_compile.c461 "number too big in {} quantifier\0"
528 "number is too big\0"
8215 } /* end of big loop */
/barrelfish-master/doc/003-hake/
H A DHake.tex541 which provides a big lattice of functions to automate generating
/barrelfish-master/usr/eclipseclp/documents/userman/
H A Dumslanguage.tex150 A good way to control printing of big structures is to write customized
/barrelfish-master/usr/eclipseclp/documents/applications/
H A Dtutorial.tex558 It is tempting to ignore warnings in order to get the code running as quickly as possible. That would be a big mistake. We should eliminate all warnings about singleton variables\index{singleton variable} and missing predicate \index{missing predicate}definitions before continuing. Not only will this lead to the detection of problems in the code at this point, we will also immediately see if new warnings are introduced when we change some part of the program.
709 Note that we can put as many parallel operations into a {\it do} loop as we want, they are all executed inside one big loop. We can of course also nest {\it do} loops so that one loop is executed inside another loop.

Completed in 152 milliseconds

12