You're mostly using ' ' to denote functions, options, commands, etc. in the document, but in some cases you're using ` ` (e.g. `-finline-functions` on line 21). The former renders verbatim, the resulting text is literally '__has_builtin', etc., while the latter is proper ASCIIDoc markup for these things, and renders in monospace font with a different color and background (same as here on pagure - -finline-functions), which I consider preferable. Can you please go through the doc and make sure to use ` ` in all of these cases?

Related to the above comment; in a few cases I noticed options, function names, etc. that should be marked up with ` ` as well, but aren't at all. For example, this should be -fprofile-generate.

If you want to make a multi-paragraph list item, then use a + on empty lines separating those paragraphs, otherwise any paragraph after the first will render as a code block instead (because it starts with multiple spaces and doesn't have the * at the start to mark it up as a list item). This problem appears a couple of times in this document.

Ok, that should be it for feedback.

Hi Petr,

Thanks for the feedback. I will make those corrections today.
I was using asciidoc program to create html from adoc file but it turns out that the output text looks different in some cases than using local preview (preview.sh).
I will remember to use local preview to check output formatting.

I've messed up with merging branches, sorry. :/
Changes are in the commit c96a9ec

Should be fine :) Thank you for your contributions!