search for: emit_llvm

...n 2004 16:49:45 -0000 1.1.1.2 > +++ i386.c 23 Dec 2004 05:31:32 -0000 > @@ -1381,9 +1381,15 @@ > error ("-malign-double makes no sense in the 64bit mode"); > if (TARGET_RTD) > error ("-mrtd calling convention not supported in the 64bit mode"); > +#if EMIT_LLVM > + /* set to standard X86 values (using 64-bit long doubles under LLVM) */ > + target_flags &= ~(MASK_SSE2 | MASK_SSE | MASK_MMX | MASK_128BIT_LONG_DOUBLE); > + ix86_fpmath = FPMATH_387; > +#else > /* Enable by default the SSE and MMX builtins. */ >...

...ropriate place to be inserting stoppoints is starting in llvm_expand_stmt, using STMT_LINENO(t) . If that's not the best place, comments would be appreciated. Using the debug_hooks seems to be a non-starter, because they're called during rtl generation, which apparently isn't done when EMIT_LLVM is set. A more pressing question is how to chain the debug intrinsics together around control flow. The current examples of debug info have no control flow except for calls. I started with a simplistic version that chained them in file order: %1 = stoppoint(%0) ... %2 = stoppoint(%1) etc.. Howev...

...rnals (and a good merge tool), so > this is probably outside the scope of an external contributor. > by "check this myself" I was talking about checking, if this is a gcc or a llvm bug by compiling and testing the outdated standalone gcc, not merging current gcc. cfrontend with EMIT_LLVM defined to 0 doesn't compile so I can't test with this source. -- Stefan Strasser