B-Lang-org/bsc

bsc crash when bs method arg name annotation doesn't match method arity

Open

#420 opened on Oct 2, 2021

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Haskell (178 forks)batch import
ICEerror-messagesgood first issue

Repository metrics

Stars
 (1,108 stars)
PR merge metrics
 (Avg merge 17d 1h) (18 merged PRs in 30d)

Description

if the arg_names annotation in a classic interface declaration has fewer names than the method has arguments, bsc crashes without any useful information:

bsc -verilog BugMethodArgNamesArity.bs
Prelude.!!: index too large

BugMethodArgNamesArity.bs is:

package BugMethodArgNamesArity where

interface ArityBug =
    foo :: Bool -> Bool -> Action {-# arg_names = [bar] #-}

{-# verilog mkArityBug #-}
mkArityBug :: Module ArityBug
mkArityBug = module
    interface
        foo _ _ = _

this specific crash occurs when !! is used in the definition of i' inside iExpandMethodLam at IExpand.hs:1065, although at least the !! in the definition of m_origion_type below has the exact same problem.

iirc the IExpand state monad handles errors, so it should be possible to check in iExpandMethodLam and emit a more informative error with a reasonable position; failing that, a quick-hack ICE with a position would also work.

Contributor guide

Research direction
Examine iExpandMethodLam in IExpand.hs around line 1065 and add a check for mismatched annotation arity, emitting an informative error message instead of crashing.
Tech stack
haskell
Domain
compilers
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Haskell
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60