[ghc-lib] internal error after removal of integer-simple

Shayne Fletcher shayne.fletcher.50 at gmail.com
Sat Jun 20 11:10:41 UTC 2020


On Fri, Jun 19, 2020 at 9:23 PM Shayne Fletcher <
shayne.fletcher.50 at gmail.com> wrote:

>
>
> On Fri, Jun 19, 2020 at 6:27 PM Ben Gamari <ben at smart-cactus.org> wrote:
>
>> On June 19, 2020 5:55:01 PM EDT, Shayne Fletcher via ghc-devs <
>> ghc-devs at haskell.org> wrote:
>> >With the recent MR that removes integer-simple in favor of ghc-bignum,
>> >I
>> >find that I get a runtime failure when I try to use ghc-lib to generate
>> >core:
>> >```
>> ># Running: stack     --no-terminal exec -- mini-compile
>> >examples/mini-compile/test/MiniCompileTest.hs
>> >
>> >examples/mini-compile/test/MiniCompileTest.hs:66:5: error:
>> >  * GHC internal error: `One' is not in scope during type checking, but
>> >it passed the renamer
>> >      tcl_env of environment: [628 :-> ATcTyCon TrName :: *,
>> >                               62b :-> APromotionErr RecDataConPE,
>> >                               62e :-> APromotionErr RecDataConPE]
>> >    * In the definition of data constructor `TrNameS'
>> >      In the data declaration for `TrName'
>> >   |
>> >66 |   = TrNameS Addr#  -- Static
>> >   |     ^^^^^^^^^^^^^
>> >mini-compile: GHC internal error: `One' is not in scope during type
>> >checking, but it passed the renamer
>> >tcl_env of environment: [628 :-> ATcTyCon TrName :: *,
>> >                         62b :-> APromotionErr RecDataConPE,
>> >                         62e :-> APromotionErr RecDataConPE]
>> >```
>> >
>> >Anyone have any pointers on what is going wrong and what I should be
>> >looking at?
>>
>> I have a hypothesis for what might be happening here. Investigating
>>
>
> Breaks at commit `96aa57878fd6e6a7b92e841a0df8b5255a559c97` (
> https://gitlab.haskell.org/ghc/ghc/-/commit/96aa57878fd6e6a7b92e841a0df8b5255a559c97)
> "Update compiler".
>

Actually it seems almost certain to be
`40fa237e1daab7a76b9871bb6c50b953a1addf23`, the linear types patch. So my
current theory is that it is probably not a bug but instead points to a
ghc-prim mismatch.

-- 
Shayne Fletcher
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20200620/f8d6ddb1/attachment.html>


More information about the ghc-devs mailing list