search for: fpcw

...I guess... I am having problems in using a (non-recommended) Fortran compiler (Salford ftn95 Windoze), and the crashes do seem to be associated with the ftn95-dervived DLL changing the Floating Point Control Word. The compiler people are suggesting (and I paraphrase!) that if R minds what the FPCW is it is up to R to make sure it is the value it wants and R should check/reset on returning from the DLL call. There seems to me to be some logic in this position - if only to make life easier for those of us who don't really know what a FPCW is! Having to add unintelligable code to reset...

On Sat, 2 Apr 2005, Ricardo wrote: > Hello, > I am trying to run a program optimized with the Pool Allocation, but I am receiving this error: > > ==================== > > *** 4 DYNAMIC POOLS INITIALIZED *** > > *** 4 DYNAMIC POOLS ALLOCATED FROM *** > > MaxHeapSize = 0.062500KB HeapSizeAtExit = 0.062500KB NOTE: only valid if using > Heuristic=AllPools and no

Hello, I am trying to run a program optimized with the Pool Allocation, but I am receiving this error: ==================== libpoolalloc.so: undefined symbol: _ZTIN4llvm16EquivClassGraphsE -load request ignored. *** 4 DYNAMIC POOLS INITIALIZED *** *** 4 DYNAMIC POOLS ALLOCATED FROM *** MaxHeapSize = 0.062500KB HeapSizeAtExit = 0.062500KB NOTE: only valid if using Heuristic=AllPools and no

...After applying the PA to it, the output is something like this: ========================== int main(void) { signed char *ltmp_2_5; struct l_struct_2E_list *l6_tmp_2E_7_2E_i2; #if defined(__GNUC__) && !defined(__llvm__) #if defined(i386) || defined(__i386__) || defined(__i386) {short FPCW;__asm__ ("fnstcw %0" : "=m" (*&FPCW)); FPCW=(FPCW&~0x300)|0x200;__asm__("fldcw %0" :: "m" (*&FPCW));} #endif #endif poolinit((&l2_GlobalPool), 4u, 4u); ltmp_2_5 = malloc(4u); l6_tmp_2E_7_2E_i2 = l1_makeList((&l2_GlobalPool), 8); *(...

.../* target machine storage layout */ +/* APPLE LOCAL begin LLVM */ +#ifdef ENABLE_LLVM +#define LONG_DOUBLE_TYPE_SIZE 64 +#else #define LONG_DOUBLE_TYPE_SIZE 80 +#endif +/* APPLE LOCAL end LLVM */ /* Set the value of FLT_EVAL_METHOD in float.h. When using only the FPU, assume that the fpcw is set to extended precision; when using Applied to gcc/gcc/config/i386/i386.h If that doesn't help, please send me a stack trace of the crash. To do this, pass -v to the failing GCC command line, then debug the cc1 invocation. In addition, please go up to the first stack frame with a GC...

Chris Lattner wrote: > Here's a new snapshot of the front-end: > http://nondot.org/sabre/2006-03-14-llvm-gcc-4.tar.gz > > This: > > 1. Fixes the inline asm problem you have above. > 2. Includes patches to make it better on Alpha's (thanks to patches by > Andrew Lenharth). > 3. Sync's it up with debug info changes in LLVM CVS (by Jim Laskey). > 4.

>> Sorry for the delay, please try this tarball: >> http://nondot.org/sabre/2006-03-02-llvm-gcc-4.tar.gz > > There's some confusion with --enable-llvm configure parameter. I've built > LLVM to a separate build dir. The source is ~ghost/Work/llvm-cvs and build > dir is /space/p2/ghost/build/llvm-cvs ... > So, it seems like, at the same time: > > 1. buildir

.../* APPLE LOCAL begin LLVM */ > +#ifdef ENABLE_LLVM > +#define LONG_DOUBLE_TYPE_SIZE 64 > +#else > #define LONG_DOUBLE_TYPE_SIZE 80 > +#endif > +/* APPLE LOCAL end LLVM */ > > /* Set the value of FLT_EVAL_METHOD in float.h. When using only the > FPU, assume that the fpcw is set to extended precision; when using > > > Applied to gcc/gcc/config/i386/i386.h > > If that doesn't help, please send me a stack trace of the crash. > To do this, pass -v to the failing GCC command line, then debug the > cc1 invocation. In addition, please go up...

We really have been trying to keep in mind that LLVM needs to support multiple front ends, which may be implementing different language standards. As much as possible, I’ve been trying to let the IEEE 754 spec drive my thinking about this, though I’ll admit that on a few points I’ve use the C99 spec as a sort of reference interpretation of IEEE 754. LLVM’s IRBuilder has been recently updated to