-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EMB2.0: Automatic stdlib size overhead adjustment #191
Comments
addressed in ace099e |
There are some issues i see with the new approach:
Perhaps it would be a better idea to compile each benchmark as a shared library with |
I'm not sure that shared libraries help if you are going to compile down for a small embedded device. One option is to use attributes to force particular functions and symbols to be retained. Would adding |
It wouldn't be possible to run them as dylibs, i just thought if you compile them as such, you remove any libraries and startup files from the elf/macho and can get an accurate size measurement for the code size.
Thanks, I'll try this attribute. This should improve --export-dynamic by also preventing inlining. |
I compared the results of either using The |
I thought it was previously discussed that embench was moving away from library subtraction in part because of issues like the ones you’ve raised, did this now change? |
We try to subtract the size overhead for libraries, startup files, crt when calculating the size of benchmarks.
Currently this is done as follows:
Issues with the current approach
New approach (planned for embench-iot 2.0)
The text was updated successfully, but these errors were encountered: