Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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 334
    • Issues 334
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 14
    • Merge requests 14
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Infrastructure Registry
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • sac-group
  • sac2csac2c
  • Issues
  • #2125

Closed
Open
Created Apr 29, 2013 by Robert Bernecky@rbeDeveloper

bug or feechur? type error reporting different between prod and dev builds.

Bugzilla Link 1073
Created on Apr 29, 2013 14:41
Resolution FIXED
Resolved on Apr 29, 2013 16:16
Version svn
OS Linux
Architecture PC
Attachments bugsdl2.sac

Extended Description

CF unit test bugsdl2.sac generates different code for the prod and dev
builds for type errors. 
The prod build #18123 gives:
 z__SSA0_1 = _type_error_( _|_);
The dev build gives:
   z__SSA0_1 = _type_error_( _|_ /* line 27 in file bugsdl2.sac:@argument #1 of "_idx_sel_" should be legal offset index into argument@#2; types found: int{-21}  and  int[4]{10,...} */);
If this is not perceived to be a bug, then perhaps someone can tell me
why we do not provide any useful debugging information to a user of the
prod build?
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking