Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • sac2c sac2c
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 403
    • Issues 403
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • sac-group
  • sac2csac2c
  • Issues
  • #1210
Closed
Open
Created May 01, 2015 by Robert Bernecky@rbeDeveloper

-b option does not accept override

Bugzilla Link 1156
Created on May 01, 2015 13:44
Version svn
OS Linux
Architecture PC

Extended Description

The sac2c unit test script  UnitTestRunGrep1 and UnitTestRunWorks1
are supposed to allow a specific unit test to override the
default compiler breakpoint by specifying their own breakpoint.
Rationale: The default might be -bopt, but a failure in WLT
required me to add my own breakpoint of -bwlt, so the
compiler invocation looks like:
   sac2c bugWLT.sac -bopt -bwlt
The -bwlt breakpoint is ignored. It looks like the compiler breaks
at the earliest breakpoint specified, which is a nuisance.
Is this behavior intentional or accidental?
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking