embench/embench-iot

Issues

• Queries on Embench benchmarks

  #98 opened 4 years ago
  2

• Issue Running Embench

  #97 opened 4 years ago
  19

• Explanation / Origin of benchmarks

  #96 opened 4 years ago
  4

• Does Wikisort need to use double precision constants ?

  #95 opened 4 years ago
  2

• How to reproduce embench for riscv32

  #94 opened 4 years ago
  11

• Standard Citation Template

  #93 opened 4 years ago
  3

• Getting started issue: Unable to build benchmarks

  #89 opened 4 years ago
  2

• Add to readme - prerequisite python version 3.x

  #87 opened 4 years ago
  0

• User guide enhancement suggestion

  #84 opened 4 years ago
  2

• Only last argument logged after benchmark fails or times out

  #83 opened 4 years ago
  0

• decoding results in run_native.py

  #81 opened 4 years ago
  0

• Python version selection

  #79 opened 4 years ago
  4

• User guide disagrees with build_all.py script

  #78 opened 4 years ago
  3

• -gc-sections is called -dead_strip in Apple's linker

  #77 opened 4 years ago
  0

• Parameter value priority order

  #76 opened 4 years ago
  2

• gcc specific attributes are used in the benchmarks

  #73 opened 4 years ago
  1

• wikisort benchmark uses gcc extensions

  #72 opened 4 years ago
  2

• No such file error if 'results' directory doesn't exist when running run_all.py

  #71 opened 4 years ago
  1

• Note in docs that pyelftools package is needed to benchmark size

  #70 opened 4 years ago
  1

• Repeated attempts to build will fail noisily

  #69 opened 4 years ago
  1

• Documentation creation of baseline results

  #68 opened 4 years ago
  0

• Control the amount of output

  #66 opened 4 years ago
  0

• cubic - quad-precision FP problem (ARM/RISCV)

  #65 opened 4 years ago
  1

• Recreating Reference Platform Size Results

  #62 opened 4 years ago
  4

• Changing int data size based on compiler used

  #60 opened 5 years ago
  1

• Benchmark speed reference values and division with CPU_MHZ

  #59 opened 5 years ago
  3

• Inconsistent Speed Results on Riscv CPU

  #53 opened 5 years ago
  4

• Misleading code size reporting when -ffunction-sections option is used

  #52 opened 5 years ago
  7

• Problems with spaces when setting tool flag options

  #51 opened 5 years ago
  3

• Benchmark files use inconsistent naming scheme

  #50 opened 5 years ago
  1

• Some of benchmarks results off for native default build

  #47 opened 5 years ago
  3

• Size of multiple sections by benchmark_size.py are not easily reported{improvement}

  #40 opened 5 years ago
  2

• Location/repository for board support files

  #39 opened 9 months ago
  2

• Avoiding Full Paths

  #38 opened 5 years ago
  1

• Empty Executable Files After Successful Compilation

  #37 opened 5 years ago
  2

• Error running benchmark

  #31 opened 5 years ago
  7

• simple primes benchmark

  #30 opened 9 months ago
  3

• Python's subprocess.run does not find crosscompilation toolchain

  #22 opened 5 years ago
  1

• Suggestion: Generate requirements.txt to list the required libraries.

  #21 opened 5 years ago
  4

• Formatted string literals is not supported in Python3.5

  #20 opened 5 years ago
  2

• Compiler optimization deletes the bodies_energy function call in the nbody benchmark.

  #16 opened 5 years ago
  3

• Benchmarks should not use assert

  #10 opened 5 years ago
  3

• Tuning the benchmark repeat rate.

  #8 opened 5 years ago
  1

• Specify target architecture

  #7 opened 5 years ago
  2

• Run benchmarks on custom system

  #6 opened 9 months ago
  4

• Some of the benchmarks are single kernels/algorithms rather than applications.

  #4 opened 5 years ago
  1

• commercial friendly license

  #3 opened 5 years ago
  3

• Trouble Running Benchmarks

  #2 opened 9 months ago
  25

• configure failed whether or not add --with-chip

  #1 opened 5 years ago
  5