Fwd: Testing network / NAT performance
rsalvaterra at gmail.com
Tue Jun 14 08:31:27 PDT 2022
[Ugh, now with less HTML, sorry about that…]
On Tue, 14 Jun 2022 at 14:20, Rafał Miłecki <zajec5 at gmail.com> wrote:
> As you can see 4e0c54bc5bc8 has accidentally moved -fno-reorder-blocks
> from !CONFIG_CC_OPTIMIZE_FOR_SIZE to CONFIG_CC_OPTIMIZE_FOR_SIZE.
> I've noticed problem with -fno-reorder-blocks long time ago, see:
> [PATCH RFC] kernel: drop -fno-reorder-blocks
> It should really get sorted out...
Why not just drop both fno-reorder-blocks and -fno-tree-ch? I have no
idea about the details, but those options seem to have been carried
forward from a time where GCC probably had issues with them (code
bloat, maybe). I've been carrying a patch in my tree for (about three)
years, dropping both options, with no issues at all in all
architectures (ARM1176JZF-S, 24Kc, 74Kc, 1004Kc, Cortex-A9,
Cortex-A53, x86-64) and GCC versions (8, 9, 10, 11, 12) I've tested.
More information about the openwrt-devel