Skip to content
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

Why the default optimization level of f-stack is O0? #711

Closed
renzibei opened this issue Oct 30, 2022 · 6 comments
Closed

Why the default optimization level of f-stack is O0? #711

renzibei opened this issue Oct 30, 2022 · 6 comments

Comments

@renzibei
Copy link
Contributor

Will there be any bugs if using higher optimization level?

@hailongeric
Copy link

I don't meet the error with O2.

@renzibei
Copy link
Contributor Author

Are you sure that you are setting the optimization level of dpdk library instead of the application code? When I change the optimization level in libs/Makefile, there would be crashes.

@hailongeric
Copy link

Sorry, I can't meet any error in running. But I meet many errors in the compiler procedure. I change some compiler's options and some src code. And make it compile successfully.

@renzibei
Copy link
Contributor Author

I also encounter compiiler errors and need to change the codes when using O2. By the way, did you comment out "FF_INET6=1"? Could you kindly share one fork of the f-stack codes with O2 enabled? Thanks!

@renzibei
Copy link
Contributor Author

After some changes to the sources of f-stack, currently I can also avoid errors in runtime.

@jfb8856606
Copy link
Contributor

Because release 1.22 and after not stable enough now, may need frequent debugging,so enable -O0 by default. And it's enable -O2 by default in release 1.21(LTS).When the latest version is stable, it will be modified to -O2 by default.

You can comment out this line in lib/Makefile to enable -O2, and hte performance will be greatly improved.
DEBUG=-O0 -gdwarf-2 -g3 -Wno-format-truncation

jfb8856606 added a commit that referenced this issue Dec 30, 2022
anvayabn pushed a commit to anvayabn/f-stack that referenced this issue Jul 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants