Commits on Source (7)
-
This patch adds an exclusion rule for `docs/users_guide/images`, to avoid lint errors of PDF files.
2d635a50 -
This patch updates the logo with a recent color scheme. This affects only the PDF version of the user's guide. See also: * https://mail.haskell.org/pipermail/ghc-devs/2020-August/019139.html * https://gitlab.haskell.org/ghc/ghc/-/wikis/logo
b7d98cb2 -
When we pretty-print a UnitId for the user, we try to map it back to its origin package name, version and component to print "package-version:component" instead of some hash. The UnitId type doesn't carry these information, so we have to look into a UnitState to find them. This is why the Outputable instance of UnitId used `sdocWithDynFlags` in order to access the `unitState` field of DynFlags. This is wrong for several reasons: 1. The DynFlags are accessed when the message is printed, not when it is generated. So we could imagine that the unitState may have changed in-between. Especially if we want to allow unit unloading. 2. We want GHC to support several independent sessions at once, hence several UnitState. The current approach supposes there is a unique UnitState as a UnitId doesn't indicate which UnitState to use. See the Note [Pretty-printing UnitId] in GHC.Unit for the new approach implemented by this patch. One step closer to remove `sdocDynFlags` field from `SDocContext` (#10143). Fix #18124. Also fix some Backpack code to use SDoc instead of String.
0b17fa18 -
There was a confusion between the boolean expected by withNewWordArrayTrimedMaybe and the boolean returned by subtracting functions.
dc476a50 -
GNU as and the AIX assembler support floating point literals. SPARC seems to have support too but I cannot test on SPARC. Curiously, `doubleToBytes` is also used in the LLVM backend. To avoid endianness issues when cross-compiling float and double literals are printed as C-style floating point values. The assembler then takes care of memory layout and endianness. This was brought up in #18431 by @hsyl20.
fcb10b6c -
There were four categories of primops: Monadic, Dyadic, Compare, GenPrimOp. The compiler does not treat Monadic and Dyadic in any special way, we can just replace them with GenPrimOp. Compare is still used in isComparisonPrimOp.
770100e0 -
Vladislav Zavialov authored86ac4dbf
Showing
- .gitlab-ci.yml 2 additions, 2 deletions.gitlab-ci.yml
- .gitlab/ci.sh 1 addition, 1 deletion.gitlab/ci.sh
- .gitlab/linters/check-cpp.py 3 additions, 0 deletions.gitlab/linters/check-cpp.py
- aclocal.m4 2 additions, 2 deletionsaclocal.m4
- compiler/GHC.hs 1 addition, 1 deletioncompiler/GHC.hs
- compiler/GHC/Builtin/PrimOps.hs 6 additions, 34 deletionscompiler/GHC/Builtin/PrimOps.hs
- compiler/GHC/Builtin/primops.txt.pp 135 additions, 137 deletionscompiler/GHC/Builtin/primops.txt.pp
- compiler/GHC/CmmToAsm/PPC/Ppr.hs 4 additions, 10 deletionscompiler/GHC/CmmToAsm/PPC/Ppr.hs
- compiler/GHC/CmmToAsm/Ppr.hs 4 additions, 20 deletionscompiler/GHC/CmmToAsm/Ppr.hs
- compiler/GHC/CmmToAsm/SPARC/Ppr.hs 22 additions, 0 deletionscompiler/GHC/CmmToAsm/SPARC/Ppr.hs
- compiler/GHC/CmmToAsm/X86/Ppr.hs 4 additions, 13 deletionscompiler/GHC/CmmToAsm/X86/Ppr.hs
- compiler/GHC/Driver/Backpack.hs 28 additions, 24 deletionscompiler/GHC/Driver/Backpack.hs
- compiler/GHC/Driver/Finder.hs 3 additions, 2 deletionscompiler/GHC/Driver/Finder.hs
- compiler/GHC/Driver/Main.hs 18 additions, 15 deletionscompiler/GHC/Driver/Main.hs
- compiler/GHC/Driver/Pipeline.hs 1 addition, 1 deletioncompiler/GHC/Driver/Pipeline.hs
- compiler/GHC/Driver/Ppr.hs 6 additions, 1 deletioncompiler/GHC/Driver/Ppr.hs
- compiler/GHC/Driver/Session.hs 1 addition, 0 deletionscompiler/GHC/Driver/Session.hs
- compiler/GHC/Driver/Types.hs 2 additions, 2 deletionscompiler/GHC/Driver/Types.hs
- compiler/GHC/Iface/Load.hs 4 additions, 1 deletioncompiler/GHC/Iface/Load.hs
- compiler/GHC/Iface/Make.hs 3 additions, 1 deletioncompiler/GHC/Iface/Make.hs