Lines Matching full:for
28 <TR><TD COLSPAN=2>5. Issues for Porting SoftFloat to a New Target</TD></TR>
35 <TR><TD></TD><TD>5.3. Macros for Build Options</TD></TR>
42 <TD COLSPAN=2>7. Providing SoftFloat as a Common Library for Applications</TD>
52 This document gives information needed for compiling and/or porting Berkeley
54 conforming to the IEEE Standard for Floating-Point Arithmetic.
55 For basic documentation about SoftFloat refer to
60 The source code for SoftFloat is intended to be relatively machine-independent
64 (<CODE>gcc</CODE>) for several platforms.
86 The C compiler used must conform at a minimum to the 1989 ANSI standard for the
93 Since 1999, ISO standards for C have mandated compiler support for
101 <CODE><stdint.h></CODE> are required for defining standard Boolean and
119 of Electrical Engineering and Computer Sciences, first for the Parallel
120 Computing Laboratory (Par Lab) and then for the ASPIRE Lab.
192 IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, ARE
194 IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
250 The <CODE>build</CODE> directory is intended to contain a subdirectory for each
251 target platform for which a build of the SoftFloat library may be created.
252 For each build target, the target’s subdirectory is where all derived
256 contain sample files for creating new target directories.
264 For the example targets,
281 The provided <CODE>Makefile</CODE> is written for GNU <CODE>make</CODE>.
282 A build of SoftFloat for the specific target is begun by executing the
289 The <CODE>platform.h</CODE> header file exists to provide a location for
291 Every C source file of SoftFloat contains a <CODE>#include</CODE> for
297 <CODE>#include</CODE>) declarations for numerous target-specific optimizations.
298 Such possibilities are discussed in the next section, <I>Issues for Porting
301 workarounds for these issues may also be possible with target-specific
307 <H2>5. Issues for Porting SoftFloat to a New Target</H2>
318 For older or nonstandard compilers, substitutes for
356 The IEEE Floating-Point Standard allows for some flexibility in a conforming
359 <I>specialization</I> subdirectories containing possible definitions for this
361 For example, the <CODE>8086</CODE> and <NOBR><CODE>8086-SSE</CODE></NOBR>
367 whether tininess for underflow is detected before or after rounding by default;
380 As provided, the build process for a target expects to involve exactly
382 implementation-specific details for the target.
394 <CODE>source</CODE> directory for this purpose.
396 specialization subdirectories can be used as a model for what definitions are
401 <H3>5.3. Macros for Build Options</H3>
410 Must be defined for little-endian machines; must not be defined for big-endian
416 For newer <NOBR>64-bit</NOBR> processors, this macro should usually be defined.
417 For very small microprocessors whose buses and registers are <NOBR>8-bit</NOBR>
419 Whether this macro should be defined for a <NOBR>32-bit</NOBR> processor may
424 <NOBR>in C</NOBR> (written as <CODE>/</CODE>) is reasonably efficient for
446 For some compilers, this macro can be defined as the single keyword
455 Following the usual custom <NOBR>for C</NOBR>, for the first three macros (all
475 provide models for new target directories.
494 <CODE>source/include</CODE>) declares macros and functions for numerous
499 built using only the supplied code for all functions.
500 However, for many targets, SoftFloat’s performance can be improved by
506 For example, <CODE>primitives.h</CODE> declares a function called
522 For this purpose, it may be helpful for <CODE>platform.h</CODE> to
524 types used for arguments and results of functions declared in
527 sufficient for <CODE>platform.h</CODE> to include the line
555 <H2>7. Providing SoftFloat as a Common Library for Applications</H2>
560 If the SoftFloat library will be made a common library for programs on a
562 deficiencies for this purpose:
566 <CODE>softfloat_types.h</CODE>, that is not intended for public use but which