1. 24 Jul, 2000 1 commit
    • simonmar's avatar
      [project @ 2000-07-24 14:29:55 by simonmar] · 1da7b45d
      simonmar authored
      Some changes to the way FFI decls are handled:
      
        - a foreign export dynamic which returns a newtype of
          an Addr now works correctly.  Similarly for foreign label.
      
        - unlifted types are not allowed in the arguments of a foreign
          export.  Previously we generated incorrect code for these cases.
      
      Newtypes in FFI declarations now work everywhere they should, as far
      as I can see.
      
      These changes will be backported into 4.08.1.
      1da7b45d
  2. 23 Jul, 2000 1 commit
    • panne's avatar
      [project @ 2000-07-23 10:53:11 by panne] · c8a6996a
      panne authored
      Strictfp-like behaviour is the default now, which can be switched off
      via -fexcess-precision. (Has anybody a better name for this option?)
      c8a6996a
  3. 21 Jul, 2000 8 commits
  4. 20 Jul, 2000 5 commits
    • rrt's avatar
      [project @ 2000-07-20 17:06:41 by rrt] · ba5a490c
      rrt authored
      What's the story, Rory?
      
         My name's not Rory. Owing to circumstances not fully understood, the RTS
         used to work DLLized, even though it was largely broken. Unfortunately,
         this was recently fixed.
      
      What used to happen?
      
         The EF_ macro from StgMacros.h was used to refer to primops &c.
      
      Why was this a Bad Thing?
      
         Because you need to use EDF_ when building with DLLs.
      
      What was the result?
      
         primops such as divExactInteger were compiled as _divExactInteger, rather
         than __imp__div_Exact_Integer, so they didn't refer to the DLL routines.
      
      How on earth did it work?
      
         I'm not sure, but somehow the code for the relevant routines got linked
         into the import libraries (e.g. libHSrts_imp.a), and were thus linked
         statically into the final binary.
      
      So that explains why the import libraries (supposedly just containing stubs)
      were larger than the DLLs they were stubbing, or the static libraries, for
      that matter?
      
         Perhaps.
      
      Golly!
      
         Indeed.
      
      What caused this code leakage?
      
         That's what I don't know. Perhaps a bug in the Cygwin DLL-building tools?
         I've upgraded from B20.1 to 1.1 recently.
      
      So, what's the hack, Mac?
      
         My name's not Mac. I added a new macro, ERTSF_, which uses DLL_IMPORT_RTS
         to make sure that the Right Thing is always done (because you mustn't
         make DLL references to RTS routines when compiling the RTS).
      
      Thanks for the chat, Matt!
      
         <punch>
      ba5a490c
    • rrt's avatar
      [project @ 2000-07-20 12:33:09 by rrt] · 8e3dd3c9
      rrt authored
      4.07->4.08
      8e3dd3c9
    • rrt's avatar
      [project @ 2000-07-20 12:32:50 by rrt] · 71e271dc
      rrt authored
      Fixed a version-o.
      71e271dc
    • rrt's avatar
      [project @ 2000-07-20 10:50:47 by rrt] · d4d93d44
      rrt authored
      &amp;gt; => &gt;
      d4d93d44
    • rrt's avatar
      [project @ 2000-07-20 10:34:42 by rrt] · 6873ca83
      rrt authored
      Updated instructions for Windows install to reflect reality as of v4.08.
      6873ca83
  5. 19 Jul, 2000 4 commits
  6. 18 Jul, 2000 13 commits
  7. 17 Jul, 2000 8 commits