Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
GHC
GHC
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 4,260
    • Issues 4,260
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 398
    • Merge Requests 398
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Glasgow Haskell Compiler
  • GHCGHC
  • Issues
  • #18326

Closed
Open
Opened Jun 11, 2020 by Sebastian Graf@sgraf812Developer

"lookupIdSubst" warnings when compiling haddock

I'm getting warnings of the form

| Run Ghc CompileHs Stage1: utils/haddock/haddock-api/src/Haddock/Types.hs => _build/stage1/utils/haddock/build/Haddock/Types.o
...
WARNING: file compiler/GHC/Core/Subst.hs, line 256
  GHC.Core.Subst.lookupIdSubst exprIsConApp1
                               subst_expr $cp1Exception_skvd
  InScope {r_ahOg a_ahOh w1_ahOk $fExceptionHaddockException}
  Call stack:
      CallStack (from HasCallStack):
        callStackDoc, called at compiler/GHC/Utils/Outputable.hs:1282:29 in ghc:GHC.Utils.Outputable
        warnPprTrace, called at compiler/GHC/Core/Subst.hs:255:18 in ghc:GHC.Core.Subst
...

Might not lead to miscompilations, but we should look into where we construct the invalid in-scope set. Judging from the size of the reported in-scope set, this should be relatively easy to pin down once reproduced locally.

Assignee
Assign to
9.2.1
Milestone
9.2.1
Assign milestone
Time tracking
None
Due date
None
Reference: ghc/ghc#18326