[Git][ghc/ghc][wip/marge_bot_batch_merge_job] 9 commits: Extend mAX_TUPLE_SIZE to 64

Marge Bot gitlab at gitlab.haskell.org
Fri Oct 16 02:29:35 UTC 2020



 Marge Bot pushed to branch wip/marge_bot_batch_merge_job at Glasgow Haskell Compiler / GHC


Commits:
6b14c418 by GHC GitLab CI at 2020-10-15T21:57:50-04:00
Extend mAX_TUPLE_SIZE to 64

As well a ctuples and sums.

- - - - -
d495f36a by Ben Gamari at 2020-10-15T21:58:27-04:00
rts: Clean-up whitespace in Interpreter

- - - - -
cf10becd by Ben Gamari at 2020-10-15T21:58:27-04:00
compiler/ByteCode: Use strict Maps in bytecode assembler

- - - - -
ae146b53 by Ben Gamari at 2020-10-15T21:58:27-04:00
compiler/ByteCode: Make LocalLabel a newtype

- - - - -
cc536288 by Ben Gamari at 2020-10-15T21:58:27-04:00
compiler/ByteCode: Allow 2^32 local labels

This widens LocalLabel to 2^16, avoiding the crash observed in #14334.

Closes #14334.

- - - - -
321df97d by John Ericson at 2020-10-15T22:29:18-04:00
Skip type family defaults with hs-boot and hsig files

Works around #17190, possible resolution for #17224. New design is is
according to accepted [GHC Propoal 320].

Instances in signatures currently unconditionally opt into associated
family defaults if no explicit instance is given. This is bad for two
reasons:

  1. It constrains possible instantiations to use the default, rather
  than possibly define the associated family differently.

  2. It breaks compilation as type families are unsupported in
  signatures.

This PR simply turns off the filling in of defaults in those cases.
Additionally, it squelches a missing definition warning for hs-boot too
that was only squelched for hsig before.

The downsides are:

  1. There is no way to opt into the default, other than copying its
  definition.

  2. If we fixed type classes in signatures, and wanted instances to
  have to explicitly *out of* rather than into the default, that would
  now be a breaking change.

The change that is most unambiguously goood is harmonizing the warning
squelching between hs-boot or hsig. Maybe they should have the warning
(opt out of default) maybe they shouldn't (opt in to default), but
surely it should be the same for both.

Add hs-boot version of a backpack test regarding class-specified
defaults in instances that appear in an hs-boot file.

The metrics increase is very slight and makes no sense --- at least no
one has figured anything out after this languishing for a while, so I'm
just going to accept it.

Metric Increase:
  T10421a

[GHC proposal 320]: https://github.com/ghc-proposals/ghc-proposals/pull/320

- - - - -
fb27b803 by Dylan Yudaken at 2020-10-15T22:29:22-04:00
When using rts_setInCallCapability, lock incall threads

This diff makes sure that incall threads, when using `rts_setInCallCapability`, will be created as locked.
If the thread is not locked, the thread might end up being scheduled to a different capability.
While this is mentioned in the docs for `rts_setInCallCapability,`, it makes the method significantly less useful as there is no guarantees on the capability being used.

This commit also adds a test to make sure things stay on the correct capability.

- - - - -
e4595fb5 by DylanZA at 2020-10-15T22:29:22-04:00
Apply suggestion to testsuite/tests/ffi/should_run/all.T
- - - - -
73b41ff2 by Hécate at 2020-10-15T22:29:24-04:00
Linting corrections

* Bring back LANGUAGE pragmas in GHC.IO.Handle.Lock.Windows
* Exclude some modules that are wrongfully reported

- - - - -


30 changed files:

- compiler/GHC/Builtin/Types.hs
- compiler/GHC/ByteCode/Asm.hs
- compiler/GHC/ByteCode/Instr.hs
- compiler/GHC/CoreToByteCode.hs
- compiler/GHC/HsToCore/Foreign/Decl.hs
- compiler/GHC/Settings/Constants.hs
- compiler/GHC/Tc/Gen/HsType.hs
- compiler/GHC/Tc/TyCl/Class.hs
- compiler/GHC/Tc/TyCl/Instance.hs
- includes/RtsAPI.h
- libraries/base/.hlint.yaml
- libraries/base/GHC/Exts.hs
- libraries/base/GHC/IO/Handle/Lock/Windows.hsc
- libraries/ghc-prim/GHC/Classes.hs
- libraries/ghc-prim/GHC/Tuple.hs
- rts/Interpreter.c
- rts/RtsAPI.c
- rts/RtsSymbols.c
- testsuite/tests/backpack/should_compile/all.T
- + testsuite/tests/backpack/should_compile/bkp57.bkp
- + testsuite/tests/backpack/should_compile/bkp57.stderr
- + testsuite/tests/backpack/should_compile/bkp58.bkp
- + testsuite/tests/backpack/should_compile/bkp58.stderr
- + testsuite/tests/backpack/should_compile/bkp59.bkp
- + testsuite/tests/backpack/should_compile/bkp59.stderr
- + testsuite/tests/backpack/should_compile/bkp60.bkp
- + testsuite/tests/backpack/should_compile/bkp60.stderr
- + testsuite/tests/ffi/should_run/IncallAffinity.hs
- + testsuite/tests/ffi/should_run/IncallAffinity_c.c
- testsuite/tests/ffi/should_run/all.T


The diff was not included because it is too large.


View it on GitLab: https://gitlab.haskell.org/ghc/ghc/-/compare/3a7025172cc0322d3b1a4756e73c25e380723154...73b41ff250c6fdf00c0fe74308f9bdf3c2303e92

-- 
View it on GitLab: https://gitlab.haskell.org/ghc/ghc/-/compare/3a7025172cc0322d3b1a4756e73c25e380723154...73b41ff250c6fdf00c0fe74308f9bdf3c2303e92
You're receiving this email because of your account on gitlab.haskell.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-commits/attachments/20201015/c10bf63d/attachment.html>


More information about the ghc-commits mailing list