USPatent applicationPatented

Division with rectangular multiplier supporting multiple precisions and operand types

Granted 14 Jun 2011 · 1 office action

Life of the application

8 dated events
⤢ drag to zoom20082010201220142016201820202022202420262028ProsecutionOwnershipTerm & fees
ProsecutionOwnershipTerm & feeshover for detail · click to open

Abstract

A division method includes determining a precision indicator for the division operation that indicates whether the quotient should be a single precision, double precision, or extended precision floating-point number. The division is performed at a rectangular multiplier using the Goldschmidt or Newton-Raphson algorithm. Each algorithm calculates one or more intermediate values in order to determine the quotient. For example, the Goldschmidt algorithm calculates a complement of a product of the dividend and an estimate of the reciprocal of the divisor. The quotient is determined based on a portion of one or more of these intermediate values. Because only a portion of the intermediate value is used, the division can be performed efficiently at the rectangular multiplier, and therefore the quotient can be determined more quickly and still achieve the desired level of precision.

Description

8 parts
›FIELD OF THE DISCLOSURE

The present disclosure relates to data processors and more particularly to floating point division operations on a data processor.

›BACKGROUND

Data processors typically employ a floating-point unit (FPU) to perform floating point arithmetic. An FPU performs arithmetic operations such as addition, subtraction, multiplication, and division. Typically, a division operation requires the FPU to execute several operations, such as several multiplication and addition operations. The faster the FPU can execute a division operation, the faster and more efficiently the data processor can execute instructions. Accordingly, there is a need for an improved method of performing a division operation on an FPU.

›BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure may be better understood, and its numerous features and advantages made apparent to those skilled in the art by referencing the accompanying drawings.

FIG. 1 is a block diagram of a particular embodiment of a data processor;

FIG. 2 is a flow diagram of a particular embodiment of a method of performing division at a rectangular multiplier;

FIG. 3 is a flow diagram of an alternative particular embodiment of a method of performing division at a rectangular multiplier; and

FIG. 4 is a block diagram of a particular embodiment of a rectangular multiplier of the data processor of FIG. 1 .

›DETAILED DESCRIPTION · 1 of 5

A method for performing division using a rectangular multiplier of a floating-point unit is disclosed. The method includes determining a precision indicator for the division operation that indicates whether the quotient should be a single precision, double precision, or extended precision floating-point number. The division is performed at a rectangular multiplier using the Goldschmidt or Newton-Raphson algorithm. Each algorithm calculates one or more intermediate values in order to determine the quotient. For example, the Goldschmidt algorithm calculates a complement of a product of the dividend and an estimate of the reciprocal of the divisor. The quotient is determined based on a portion of one or more of these intermediate values. Because only a portion of the intermediate value is used, the division can be performed efficiently at the rectangular multiplier, and therefore the quotient can be determined more quickly and still achieve the desired level of precision.

Referring to FIG. 1 , a block diagram of a particular embodiment of a data processor 100 is illustrated. The data processor 100 includes an instruction pipeline 105 and a cache 110 . The instruction pipeline 105 includes fetch stages 121 , a dispatch stage 123 , a plurality of execution units including execution units 124 and 125 , a floating-point unit 126 , and post execution stages 128 .

The fetch stages 121 are illustrated as having a bi-directional connection to the cache 110 in that the fetch stages 121 are able to provide an address to the cache 110 and receive data based on the address. The fetch stages 121 also include an output. The dispatch stage 123 includes an input connected to the output of the fetch stages 121 and three outputs. The execution unit 124 includes an input connected to a first output of the dispatch stage 123 and an output. The execution unit 125 includes an input connected to a second output of the dispatch stage 123 and an output. The floating-point unit 126 includes an input connected to a third output of the dispatch stage 123 and an output. The post execution stages 128 include an input connected to the output of the execution unit 124 , an input connected to the output of the execution unit 125 , and an input connected to the output of the floating-point unit 126 .

The cache 110 stores data for the instruction pipeline 105 , including instruction data and operand data. It will be appreciated that although the cache 110 is illustrated as a single cache, it can represent multiple caches, such as separate caches for instruction data and operand data. In addition, the cache 110 may be accessible to other stages of the instruction pipeline 105 , even though specific connections to the stages are not illustrated. For example, the execution units, such as the execution units 124 and 125 , may be able to access the cache 110 to retrieve and store data.

During operation, the instruction pipeline 105 executes instructions at the data processor 100 . To execute an instruction, the fetch stages 121 fetch instruction data from the cache 110 . The fetch stages 121 decode the instruction data to obtain instruction information and, based on the instruction information, retrieve operand data from the cache 110 . For example, in the case of a division instruction, the fetch stages 121 can retrieve the divisor and dividend from the cache 110 .

The fetch stages 121 provides the instruction information and the operand data to the execution unit 124 , the execution unit 125 , or the floating-point unit 126 for execution. For example, if the instruction information indicates that the instruction requires a floating point operation, the instruction information and the operand data is provided to the floating-point unit 126 .

The execution units 124 and 125 , as well as the floating-point unit 126 , provide the instruction information to the post-execution stages 128 , which provides post-execution processing of the information. For example, the post-execution stages 128 can retire instructions, detect exceptions resulting from execution of the instructions, and the like.

The floating-point unit 126 executes instructions that require floating point operations, including addition, subtraction, multiplication, and division. The floating-point unit 126 includes a multiplier 130 to execute multiplication and division operations. In a particular embodiment, the multiplier 130 is a rectangular multiplier. A rectangular multiplier is characterized by having input operands of different sizes. For example, a 27×76 rectangular multiplier uses one operand of 27 bits and another of 76 bits. To execute a division operation, the floating-point unit 126 receives operand information from the dispatch stage 123 , including a divisor and dividend. The dispatch stage 123 also provides instruction information, including a precision indicator to indicate whether the quotient should be a single precision value, a double precision value, or an extended precision value according to a specific standard, such as the IEEE-754 Standard for Binary Floating Point Arithmetic. The precision indicator can include precision control information that indicates the desired level of precision of the quotient, as well as operand type information that indicates the precision level of the division operands.

In one embodiment, the floating-point unit 126 uses a Goldschmidt algorithm to perform division. The Goldschmidt algorithm computes the quotient Q=A/B by determining an estimate of the divisor's reciprocal:

X 0 ≈ 1 B

The following values are then determined:

N 0 =X 0 ×A

D 0 =X 0 ×B

R 0 =2− D 0

Subsequently, m−1 iterations are performed to calculate the following values:

N i+1 =R i ×N i

D i+1 =R i ×D i

R i+1 ==2− D i−1

Once the m−1 iterations have been performed, the quotient Q is obtained as follows:

Q=N m+1 ×R m+1

The number of iterations depends on the desired level of precision of the quotient Q as well as the accuracy of the estimate X 0 . Accordingly, the less accurate the estimate X 0 and the higher the desired level of precision for the quotient Q, the greater the number of iterations performed before the quotient is determined.

›DETAILED DESCRIPTION · 2 of 5

In a particular embodiment, reduced values for R i , including R 0 , are used to calculate the N i and D i values and the quotient Q. As used herein, the term reduced means that one or more of the most significant bits, one or more of the least significant bits, or both are removed from a binary value. For example, the value R 0 may be a 76 bit value, and can be reduced by removing its least significant bits so that the reduced value is a 30 bit value. In addition, the R i values may be reduced by different amounts for different iterations. For example, the value R 0 may be reduced to a 30 bit value while the value R 1 is reduced to a 60 bit value. By reducing the values for R i , the division operations can be executed more efficiently at the multiplier 130 than with a multiplier that uses operands of equal sizes, while still achieving the desired level of precision for the quotient Q.

In another embodiment, the floating-point unit 126 uses a Newton-Raphson algorithm to determine the quotient Q=A/B. The floating-point unit determines the estimate of the divisor's reciprocal:

X 0 ≈ 1 B

and performs m iterations of the following equations:

R i =2− X i ×B

X i+1 =X i ×R i

After m iterations of these equations, X m is multiplied by A to obtain the quotient Q. The number of iterations depends on the desired level of precision of the quotient Q as well as the accuracy of the estimate X 0 .

In a particular embodiment, reduced values for R i , and X i are used to calculate the R i and X i+1 values and the quotient Q. In addition, the values may be reduced by different amounts for different iterations. By reducing the values for R i and X i , the division operations can be executed more efficiently at the multiplier 130 while still achieving the desired level of precision for the quotient Q.

Referring to FIG. 2 , a flow diagram of a particular embodiment of a method 200 to determine a quotient Q with a rectangular multiplier is shown.

At block 202 input values are received, including a dividend A, a divisor B, a precision control indicator PC, an operand type indicator OT, and a rounding control indicator RC. The operand type indicator OT indicates whether the operands, including dividend A and the divisor B are single precision operands, double precision operands, or extended precision operands. The precision control information PC indicates the desired precision of the quotient when the operand type indicator OT indicates the operands are extended precision values. The rounding control indicator RC indicates whether the quotient Q f should be rounded to the nearest-even, rounded toward zero, rounded toward minus infinity, or rounded toward plus infinity.

At block 204 , the reciprocal estimate (X 0 ) of the divisor B is determined. The reciprocal estimate can be determined using a lookup table or other method. In a particular embodiment, the reciprocal estimate is determined using 2 10 by 16 and 2 10 by 7 bipartite tables to provide a reciprocal estimate accurate to at least 14.94 bits.

At block 206 , values D 0 , R 0 , and N 0 are calculated. The value D 0 is calculated by performing a rectangular multiplication of the value X 0 and the divisor B. As used herein, the term “rectangular multiplication” refers to a multiplication using operands of different sizes. For example, a 27×76 rectangular multiplier performs a multiplication of a first operand with a size of 27 bits and a second operand with a size of 76 bits. In a preferred embodiment, the size of the first operand can be increased by iteratively performing multiplication operations at the rectangular multiplier. For example, the 27×76 rectangular multiplier can perform a 54×76 rectangular multiply be executing two iterative multiplications and one addition at the multiplier.

At block 206 , the value R 0 is determined by calculating the 1's compliment of D 0 . The value N 0 is determined by performing a rectangular multiplication of the dividend A and the value X 0 . In an exemplary embodiment where the reciprocal estimate X 0 is accurate to at least 14.94 bits, the values D 0 and N 0 are accurate to at least 27 bits.

At block 208 , it is determined whether the operand type indicator indicates that the received operands are single precision values. If so, the method flow proceeds to block 210 and a value Q i is determined based on the value N 0 and a value based on a portion of the value R 0 . In a particular embodiment, the value R 0 is reduced by removing one or more of its least significant bits to form a reduced complement value. The value Q i is determined by performing a rectangular multiplication of the value N 0 with the reduced complement value R 0 . By using a reduced complement value, the multiplication can be performed with fewer iterations at the rectangular multiplier, thereby improving the efficiency of the division operation while still obtaining a desired level of precision of the quotient.

In another embodiment, the value R 0 is reduced by removing one or more most significant bits and one or more least significant bits from the value to form a reduced R 0 value. The value Q i is determined by performing a fused rectangular multiplication and add operation, where a rectangular multiplication is performed using the truncated R 0 value and the value N 0 and the result is added to the value N 0 . In a particular embodiment, the value R 0 is a 76 bit value and the truncated R 0 value is formed by bits 13 - 39 of the value R 0 .

At block 212 the value Q i is rounded, based on the rounding control RC, to 24 bits of precision to obtain the single precision floating-point quotient Q f . To determine how the quotient will be rounded, a remainder REM is determined by performing a rectangular multiplication of the divisor B by the value Q i , and subtracting the result from the dividend A. The remainder REM indicates if the value Q i is greater than, less than, or equal to the true quotient Q. In an exemplary embodiment, in response to the rounding control indicator RC indicating the result Q f should not be less than the quotient Q, the rounding ensures that the single precision result Q f is greater than or equal to the quotient Q. In an alternative embodiment, in response to the rounding control indicator RC indicating the result Q f should not be more than the quotient Q, the rounding can ensure that the single precision result Q f is less than or equal to the quotient Q. At block 226 , the rounded single precision quotient value Q f is provided.

›DETAILED DESCRIPTION · 3 of 5

Returning to block 208 , if it is determined that the operand type indicator OT indicates that the operands are not single precision values, the method flow moves to block 216 . At block 216 , it is determined whether the operand type indicator OT indicates that the operands are extended precision values and whether the precision control indicates that the quotient result should be a single precision value. If so, the method flow moves to block 228 , described below. If not, the method flow moves to block 218 , and a value D 1 , a value R 1 , and a value N 1 are determined. In one embodiment, the value D 1 is calculated by removing one or more of the least significant bits from the value R 0 to form a reduced complement value and performing a rectangular multiplication of the values D 0 and the reduced complement value based on the value R 0 . In a particular embodiment, the value R 0 is a 76 bit value and the reduced complement value is formed by the 54 most significant bits of R 0 . In addition, the value N 1 is calculated by performing a rectangular multiplication of the values N 0 and the reduced complement value R 0 . The value R 1 is determined by computing the complement of the value D 1 .

In an alternative embodiment, the reduced complement value is formed by removing one or more of the least significant bits and one or more of the most significant bits of the value R 0 . In a particular embodiment, R 0 is a 76 bit value and the reduced complement value is formed by bits 13 - 39 of the value R 0 . The value D 1 is calculated by performing a multiply-add operation at a rectangular multiplier with the reduced complement value and the value D 0 . The value N 1 is calculated by performing a multiply-add operation at a rectangular multiplier with the reduced complement value and the value D 0 . The value R 1 is determined by determining the complement of the value D 1 .

At block 220 , it is determined whether the operand type indicator OT indicates that the operand types are double precision values. If so, the method flow moves to block 222 . At block 222 , a quotient value Q i is calculated. In one embodiment, the quotient value Q i is calculated by performing a rectangular multiplication of the values R 1 and N 1 .

In another embodiment, a reduced complement value is formed by removing one or more least significant bits from the value R 1 . In a particular embodiment, R 0 is a 76 bit value and the reduced complement value is formed by bits 26 - 75 of the value R 0 . The quotient value Q i is calculated by performing a multiply-add operation at a rectangular multiplier using the reduced complement value and the value N 1 .

At block 224 , a remainder REM is determined by performing a rectangular multiplication of the quotient value Q i and the divisor B and subtracting the result from the dividend A. The remainder REM indicates if the value Q i is greater than, less than, or equal to the quotient Q. Based on this information, and the rounding control indicator RC, the quotient value Q i is rounded to obtain the quotient Q f . For example, in response to the rounding control indicator RC indicating the result Q f should not be less than the quotient Q, the rounding ensures that the single precision result Q f is greater than or equal to the quotient Q. In an alternative embodiment, in response to the rounding control indicator RC indicating the quotient value Q f should not be more than the quotient Q, the rounding can ensure that the single precision quotient value Q f is less than or equal to the quotient Q. At block 226 , the quotient value result Q f is provided.

Returning to block 220 , if the operand type indicator OT does not indicate that the operands are double precision operands, the method flow moves to block 228 . At block 228 , it is determined whether the precision control indicator PC indicates that the quotient value should be a single precision value. If not, the method flow moves to block 230 .

At block 230 , it is determined whether the precision control indicator PC indicates that the quotient value should be a double precision value. If not, the method flow moves to block 232 . At block 232 , values N 2 , R 2 and D 2 are calculated. In a particular embodiment, the value N 2 is calculated by performing a rectangular multiplication of the values R 1 and N 1 , the value D 2 is calculated by performing a rectangular multiplication of the values R 1 and D 1 , and the value R 2 is calculated by determining a complement value of the value D 2 .

In another embodiment, a reduced R 1 value is formed by removing one or more of the least significant bits and one or more most significant bits of the value R 1 . In a particular embodiment, the reduced R 1 value is the value of bits 26 - 75 of the value R 1 . The value N 2 is calculated by performing a multiply-add operation using the reduced R 1 value and the value N 1 . The value D 2 is calculated by performing a multiply-add operation using the reduced R 1 value and the value D 1 . The value R 2 is calculated by determining a complement value of the value D 2 .

The method flow moves to block 234 , and a quotient value Q i is determined by performing a rectangular multiplication operation on the value R 2 and the value N 2 . The method flow moves to block 240 , and a remainder REM is calculated by performing a rectangular multiplication of the divisor B and the value Q i and subtracting the result from the dividend A. The remainder REM indicates if the value Q i is greater than, less than, or equal to the quotient Q. Based on the remainder REM and the rounding control indicator RC, the quotient Q f is determined. In an exemplary embodiment, in response to the rounding control indicator RC indicating the result Q f should not be less than the quotient Q, the rounding ensures that the single precision result Q f is greater than or equal to the quotient Q. In an alternative embodiment, in response to the rounding control indicator RC indicating the result Q f should not be more than the quotient Q, the rounding can ensure that the single precision result Q f is less than or equal to the quotient Q. The method flow proceeds to block 226 and the quotient Q f is provided.

›DETAILED DESCRIPTION · 4 of 5

At block 230 , in response to the operand type indicator OT indicating the operands are double precision operands, the method flow moves to block 238 . At block 238 , the quotient value Q i is calculated. In a particular embodiment, the quotient Q i is calculated by performing a rectangular multiplication on the values N 1 and R 1 .

In another embodiment, a reduced complement value is formed by removing one or more most significant bits from the value R and the quotient value Q i is calculated by performing a multiply-add operation at a rectangular multiplier using the reduced complement value and the value N 1 . In a particular embodiment, R 0 is a 76 bit value and the reduced complement value is formed by bits 26 - 75 of the value R 0 .

At block 228 , in response to the operand type indicator OT indicating the operands are single precision operands, the method flow moves to block 236 . At block 236 , the quotient value Q i is calculated. In a particular embodiment, the quotient value Q i is determined based on the value N 0 and a value based on a portion of the value R 0 . In a particular embodiment, the value R 0 is reduced by removing one or more of its least significant bits to form a reduced complement value. The value Q i is determined by performing a rectangular multiplication of the value N 0 with the reduced complement value.

In another embodiment, the value R 0 is reduced by removing one or more most significant bits and one or more least significant bits from the value to form a reduced R 0 value. The value Q i is determined by performing a rectangular multiplication and add operation, where a rectangular multiplication is performed using the reduced R 0 value and the value N 0 and the result is shifted and added to the value N 0 . In a particular embodiment, the value R 0 is a 76 bit value and the reduced R 0 value is formed by bits 13 - 39 of the value R 0 .

Referring to FIG. 3 , an exemplary method to determine a quotient Q is shown and generally designated 300 . At block 302 input values are received, including a dividend A, a divisor B, a precision control indicator PC, an operand type indicator OT, and a rounding control indicator RC. The operand type indicator OT indicates whether the operands, including dividend A and the divisor B are single precision operands, double precision operands, or extended precision operands. The precision control information PC indicates the desired precision of the quotient while the operand type indicator OT indicates the operands are extended precision values. The rounding control indicator RC indicates whether the quotient Q f should be rounded to the nearest-even, rounded toward zero, rounded toward minus infinity, or rounded toward plus infinity.

At block 304 , the reciprocal estimate (X 0 ) of the divisor B is determined. The reciprocal estimate can be determined using a look up table or other method. In a particular embodiment, the reciprocal estimate is determined using 2 10 by 16 and 2 10 by 7 bipartite tables to provide a reciprocal estimate accurate to at least 14.94 bits.

At block 306 , the value R 0 is determined by performing a rectangular multiplication of the divisor B and the reciprocal estimate X 0 and calculating the 1's compliment of the result. At block 308 , the value X 1 is calculated by multiplying the values X 0 and R 0 .

At decision block 310 , it is determined if the operand type indicator OT indicates that the operands A and B are single precision values. If so, the method flow moves to block 312 and the quotient value Q i is calculated by performing a rectangular multiplication of the values A and X 1 . The method flow proceeds to block 314 and the value Q i is rounded, based on the rounding control RC, to obtain the single precision floating-point quotient Q i . To determine how the quotient will be rounded, a remainder REM is determined by performing a rectangular multiplication of the divisor B by the value Q i , and subtracting the result from the dividend A. The remainder REM indicates if the value Q i is greater than, less than, or equal to the true quotient Q. In an exemplary embodiment, in response to the rounding control indicator RC indicating the result Q f should not be less than the quotient Q, the rounding ensures that the single precision result Q f is greater than or equal to the quotient Q. In an alternative embodiment, in response to the rounding control indicator RC indicating the result Q f should not be more than the quotient Q, the rounding can ensure that the single precision result Q f is less than or equal to the quotient Q. At block 316 , the rounded single precision quotient value Q f is provided.

Returning to block 310 , if the operand type indicator OT indicates that the operands are not single precision values, the method flow moves to decision block 318 . At block 318 , it is determined if the operand type indicator OT indicates that the operands are extended precision values and the precision control indicates that the quotient value should be a single precision value. If not, the method flow moves to block 320 . At block 320 , the value R 1 is calculated by reducing the value X 1 , performing a rectangular multiplication of the divisor B and the reduced X 1 value, and determining a complement of the result. In a particular embodiment, the value X 1 is a 76 bit value and the reduced X 1 value is formed using bits 0 - 26 of the value X 1 .

The method flow moves to block 322 and the value X 2 is calculated by performing a rectangular multiplication of the reduced X 1 value and the value R 1 . The method flow proceeds to decision block 324 , and it is determined whether the operand type indicator OT indicates that the operands are double precision values. If so, the method flow proceeds to block 326 .

At block 326 , the quotient value Q i is calculated by performing a rectangular multiplication of the values A and X 2 . The method flow proceeds to block 328 and the value Q i is rounded, based on the rounding control RC, to obtain the single precision floating-point quotient Q f . To determine how the quotient will be rounded, a remainder REM is determined by performing a rectangular multiplication of the divisor B by the value Q i , and subtracting the result from the dividend A. The remainder REM indicates if the value Q i is greater than, less than, or equal to the true quotient Q. The quotient value Q f is provided at block 316 .

›DETAILED DESCRIPTION · 5 of 5

Returning to block 324 , if the operand type indicator OT indicates the operands are not double precision values, the method flow proceeds to block 332 . In addition, at block 318 if the operand type indicator OT indicates the operands are extended precision values and the precision control indicates that the quotient should be a single precision value, the method flow moves to block 332 .

At block 332 , it is determined whether the precision control indicator PC indicates that the quotient should be a single precision value. If so, the method flow moves to block 346 and the quotient value Q i is calculated by performing a rectangular multiplication of the value X 1 and a truncated value of the dividend A. In a particular embodiment, the dividend A is a 76 bit value, and the truncated A value is formed based on bits 0 - 26 of the value A.

The method flow proceeds to block 342 and the value Q i is rounded, based on the rounding control RC, to obtain the single precision floating-point quotient Q f . To determine how the quotient will be rounded, a remainder REM is determined by performing a rectangular multiplication of the divisor B by the value Q i , and subtracting the result from the dividend A. The remainder REM indicates if the value Q i is greater than, less than, or equal to the true quotient Q. The quotient value Q f is provided at block 316 .

If, at block 332 , it is determined that the precision control indicator PC does not indicate that the quotient should be a single precision value, the method flow moves to decision block 334 . At block 334 , it is determined whether the precision control indicator PC indicates that the quotient should be a double precision value. If so, the method flow moves to block 346 and the quotient value Q i is calculated by performing a rectangular multiplication of the value X 2 and the dividend A. The method flow proceeds to block 342 , described previously.

If, at block 334 , it is determined that the precision control indicator PC does not indicate that the quotient should be a double precision value, the method flow moves to block 336 and the value R 2 is calculated by reducing the value X 2 to determine a reduced X 2 value, performing a rectangular multiplication of the divisor value B and the reduced X 2 value determining a complement of the result. In a particular embodiment, the value X 2 is a 76 bit value and the reduced X 2 value is formed using bits 0 - 53 of the value X 2 . The method flow moves to block 338 and the value X 3 is calculated by performing a rectangular multiplication of the values X 2 and R 2 . The method flow proceeds to block 340 and the quotient value Q i is calculated by performing a rectangular multiplication of the values A and X 3 . The method flow proceeds to block 342 , described previously.

Referring to FIG. 4 , a particular embodiment of a rectangular floating point multiplier 430 , corresponding to the multiplier 130 of FIG. 1 is illustrated. The rectangular floating-point multiplier is implemented in two pipeline stages as shown in FIG. 4 . The first stage 402 includes of a 76-bit×27-bit multiplier which accepts a 76-bit feedback term in a redundant carry-save format and produces a 103-bit product in a redundant carry-save format. The second stage 404 includes combined rounding and addition, result multiplexing and finally forwarding to the register file and bypass networks. The multiplier 430 supports a range of precisions with wider precision multiplies achieved by multiple passes through the first stage. The supported precisions include 24×24, 25×24, 27×76, 53×53, 54×53, 54×76, 66×66, 68×68 and 76×76. The multiplier also supports two single precision (dual 24×24) multiplications in parallel.

For each pass through the multiplier 430 the appropriate 27-bits of the multiplier operand are selected by the Unpack/Align Multiplexers. Two sets of radix-4 Booth encoders are required to support the dual 24-bit by 24-bit multiplication mode. The Booth multiplexers produce fourteen 81-bit partial products which are compressed along with the two 76-bit feedback terms using a partial product reduction tree implemented using 3 levels of 4-2 compressors. For the first pass the feedback terms are all zeros. For subsequent passes, the feedback terms are obtained from the upper 76-bits of the carry-save product produced by the previous pass.

The rounding scheme implemented in the second stage 404 involves adding a rounding constant to the carry-save product using a 3-2 carry-save adder prior to the addition. The rounding is performed prior to normalization using two additions, with one addition assuming no overflow occurs and one addition assuming overflow occurs. A third addition computes the unrounded mantissa. Since for wider precision multiplies the product generation is split over multiple cycles, the lower 27-bits are processed after each pass to compute sticky and the carry-in for the next pass. The appropriate rounding constant is taken into account for the first two additions and is omitted for the unrounded mantissa, which requires two separate carry trees.

Claims as granted

20 claims

Log in to read the claims of this application.

Log in to unlock

Classifications

2 codes
IPC · International Patent Classification
Section G — Physics
  • G06F7/535
USPC · US Patent Classification
708/654

Claim changes

Soon
Coming soonHow the claims changed between publication and grant

See which claims were amended, added or cancelled during examination, with every added and removed word marked.

AmendedAddedCancelledUnchanged

The published claims of this application are not paired with the granted ones in what we hold.

File wrapper

⤢ drag to zoomJul 2007Jan 2008Jul 2008Jan 2009Jul 2009Jan 2010Jul 2010Jan 2011Jul 2011USPTOApplicantNon-final rejectionNotice of allowance
USPTOApplicanthover for detail · click to open
Pendency
4.0 y
1,474 days filing → grant
Office actions
1
non-final + final
Responses
1
no RCE
Examiner
David H Malzahn
art unit 2193 · TC 2100
Citations: 29 back · 21 forward

See the full prosecution history — every USPTO and applicant action on this file, in order.

Log in to unlock

Documents

Log in to open the documents of this file: the application as filed, every office action and response, the notice of allowance.

Log in to unlock

Chain of title

⤢ drag to zoom20082010201220142016201820202022202420262028Owner 1
Titlehover for detail · click to open

See the full assignment history — every owner this patent has passed through, with recordation dates and reel/frame numbers.

Log in to unlock