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
  • #2301
Closed
Open
Created Feb 24, 2022 by Robert Bernecky@rbeDeveloper

Confusion about gettime()

sac@medusa:~/sac/benchmarks/LivermoreLoops/loop01$ sac2c -V
sac2c 1.3.3-MijasCosta-774-g4dc6e2
build-type: RELEASE
built-by: "sac" at 2022-02-24T14:24:00
sac@medusa:~/sac/benchmarks/LivermoreLoops/loop01$ sac2c loop01.sac 
sac@medusa:~/sac/benchmarks/LivermoreLoops/loop01$ time a.out < loop01.inp 
Running Loop1_APL2
Number of repetitions: 1000000
Vector length        : 1001
Upper limit (n)      : 990


*** SAC runtime error
*** When the stdlib was compiled for this architecture neither clock_gettime( CLOCK_REALTIME, x)  nor 
host_get_clock_service(mach_host_self(), CALENDAR_CLOCK, x) were found

I ran into this before. Rebuilt Stdlib, and it thinks we have a clock:

 * Configuration state:
 * - realtime clock:       1
 * - mach clock:           

I had this happen several days ago, and found that rebuilding sac2c and Stdlib "fixed" it. I will rebuild things again, and see what I get.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking