diff options
author | Peter Johnson <peter@tortall.net> | 2003-10-02 05:03:50 +0000 |
---|---|---|
committer | Peter Johnson <peter@tortall.net> | 2003-10-02 05:03:50 +0000 |
commit | 55438b722983d01811f5edf1ecfc86df3d2dd31c (patch) | |
tree | e944694581a253d32d593b69f0bdabde8be02dbc /libyasm/floatnum.c | |
parent | 18b2af8355f76ea9fb1c883488d4ca8046766453 (diff) | |
download | yasm-55438b722983d01811f5edf1ecfc86df3d2dd31c.tar.gz |
Massive libyasm / module interface update - Phase 1
As yasm has evolved, various minor additions have been made to libyasm to
support the new features. These minor additions have accumulated, and
some contain significant redundancies. In addition, the core focus of
yasm has begun to move away from the front-end commandline program "yasm"
to focusing on libyasm, a collection of reusable routines for use in all
sorts of programs dealing with code at the assembly level, and the modules
that provide specific features for parsing such code.
This libyasm/module update focuses on cleaning up much of the cruft that
has accumulated in libyasm, standardizing function names, eliminating
redundancies, making many of the core objects more reusable for future
extensions, and starting to make libyasm and the modules thread-safe by
eliminating static variables.
Specific changes include:
- Making a symbol table data structure (no longer global). It follows a
factory model for creating symrecs.
- Label symbols now refer only to bytecodes; bytecodes have a pointer to
their containing section.
- Standardizing on *_create() and *_destroy() for allocation/deallocation.
- Adding a standardized callback mechanism for all data structures that
allow associated data. Allowed the removal of objfmt and
dbgfmt-specific data callbacks in their interfaces.
- Unmodularizing linemgr, but allowing multiple linemap instances (linemgr
is now renamed linemap).
- Remove references to lindex; all virtual lines (from linemap) are now
just "line"s.
- Eliminating the bytecode "type" enum, instead adding a standardized
callback mechanism for custom (and standard internal) bytecode types.
This will make it much easier to add new bytecodes, and eliminate the
possibility of type collisions. This also allowed the removal of the
of_data and df_data bytecodes, as objfmts and dbgfmts can now easily
implement their own bytecodes, and the cleanup of arch's bytecode usage.
- Remove the bytecodehead and sectionhead pseudo-containers, instead
making true containers: section now implements all the functions of
bytecodehead, and the new object data structure implements all the
functions of sectionhead.
- Add object data structure: it's a container that contains sections, a
symbol table, and a line mapping for a single object. Every former use
of sectionhead now takes an object.
- Make arch interface and all standard architectures thread-safe:
yasm_arch_module is the module interface; it contains a create()
function that returns a yasm_arch * to store local yasm_arch data; all
yasm_arch_module functions take the yasm_arch *.
- Make nasm parser thread-safe.
To be done in phase 2: making other module interfaces thread-safe. Note
that while the module interface may be thread-safe, not all modules may be
written in such a fashion (hopefully all the "standard" ones will be, but
this is yet to be determined).
svn path=/trunk/yasm/; revision=1058
Diffstat (limited to 'libyasm/floatnum.c')
-rw-r--r-- | libyasm/floatnum.c | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/libyasm/floatnum.c b/libyasm/floatnum.c index e9addc28..4c117e1b 100644 --- a/libyasm/floatnum.c +++ b/libyasm/floatnum.c @@ -303,7 +303,7 @@ floatnum_mul(yasm_floatnum *acc, const yasm_floatnum *op) } yasm_floatnum * -yasm_floatnum_new(const char *str) +yasm_floatnum_create(const char *str) { yasm_floatnum *flt; int dec_exponent, dec_exp_add; /* decimal (powers of 10) exponent */ @@ -503,7 +503,7 @@ yasm_floatnum_copy(const yasm_floatnum *flt) } void -yasm_floatnum_delete(yasm_floatnum *flt) +yasm_floatnum_destroy(yasm_floatnum *flt) { BitVector_Destroy(flt->mantissa); yasm_xfree(flt); @@ -511,10 +511,10 @@ yasm_floatnum_delete(yasm_floatnum *flt) void yasm_floatnum_calc(yasm_floatnum *acc, yasm_expr_op op, - /*@unused@*/ yasm_floatnum *operand, unsigned long lindex) + /*@unused@*/ yasm_floatnum *operand, unsigned long line) { if (op != YASM_EXPR_NEG) - yasm__error(lindex, + yasm__error(line, N_("Unsupported floating-point arithmetic operation")); else acc->sign ^= 1; @@ -660,7 +660,7 @@ floatnum_get_common(const yasm_floatnum *flt, /*@out@*/ unsigned char *ptr, int yasm_floatnum_get_sized(const yasm_floatnum *flt, unsigned char *ptr, size_t destsize, size_t valsize, size_t shift, - int bigendian, int warn, unsigned long lindex) + int bigendian, int warn, unsigned long line) { int retval; if (destsize*8 != valsize || shift>0 || bigendian) { @@ -684,10 +684,10 @@ yasm_floatnum_get_sized(const yasm_floatnum *flt, unsigned char *ptr, } if (warn) { if (retval < 0) - yasm__warning(YASM_WARN_GENERAL, lindex, + yasm__warning(YASM_WARN_GENERAL, line, N_("underflow in floating point expression")); else if (retval > 0) - yasm__warning(YASM_WARN_GENERAL, lindex, + yasm__warning(YASM_WARN_GENERAL, line, N_("overflow in floating point expression")); } return retval; @@ -708,7 +708,7 @@ yasm_floatnum_check_size(/*@unused@*/ const yasm_floatnum *flt, size_t size) } void -yasm_floatnum_print(FILE *f, const yasm_floatnum *flt) +yasm_floatnum_print(const yasm_floatnum *flt, FILE *f) { unsigned char out[10]; unsigned char *str; |