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
  • #2239

Closed
Open
Created Oct 26, 2018 by Artem Shinkarov@temaOwner

-DBUILDGENERIC doesn't propagate to runtime libraries

Currently, we use -DBUILDGENERIC=ON to make sure that sac2c is not relying on the exact architecture that it is being compiled on. This is needed when creating packages, so that they work on a larger set of cpus.

However, while BUILDGENERIC does the right thing for sac2c, default sac2c flags for compiling sac programs, contain -march=native -mtune=native. Unfortunately, these very flags are used when building runtime libraries. As a result, runtime libraries may contain illegal instructions.

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