embench/embench-iot

Benchmark files use inconsistent naming scheme

BrianGraysonSiV opened this issue · 1 comments

Many of the benchmarks have the main code in a file of the form src/<benchname>/<benchname>.c. But there are several different benchmarks that violate this:

  • aha-mont64/mont64.c -- why not aha-mont64.c?
  • cubic/libcubic.c -- why not cubic.c? (same goes for many others)
  • qrduino/qrtest.c -- why not qrduino.c? (same goes for sglib-combined)
  • crc32/crc_32.c -- why not crc32.c?

Is there a good reason to NOT rename them in order to ensure a bit of sanity? (I realize they may have come from all sorts of other original sources.)

@BrianGraysonSiV

Thanks for raising this. It is a legacy of the old autotools based build system when we had to build things as libraries first.

I've marked it as an enhancement. There is no reason why we can't have naming consistency in the future.