summaryrefslogtreecommitdiff
path: root/Documentation/devicetree/bindings/slimbus
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2020-01-07 23:05:43 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2020-01-14 23:46:47 +0300
commit7483e7a939c074d887450ef1c4d9ccc5909405f8 (patch)
treed7cd5d66d78959ab35f9f674ded1ed3458b977b8 /Documentation/devicetree/bindings/slimbus
parente2f9d739b2877ddd43bb3132f837c80ed5430e39 (diff)
downloadlinux-7483e7a939c074d887450ef1c4d9ccc5909405f8.tar.xz
vme: bridges: reduce stack usage
With CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE_O3, the stack usage in vme_fake grows above the warning limit: drivers/vme/bridges/vme_fake.c: In function 'fake_master_read': drivers/vme/bridges/vme_fake.c:610:1: error: the frame size of 1160 bytes is larger than 1024 bytes [-Werror=frame-larger-than=] drivers/vme/bridges/vme_fake.c: In function 'fake_master_write': drivers/vme/bridges/vme_fake.c:797:1: error: the frame size of 1160 bytes is larger than 1024 bytes [-Werror=frame-larger-than=] The problem is that in some configurations, each call to fake_vmereadX() puts another variable on the stack. Reduce the amount of inlining to get back to the previous state, with no function using more than 200 bytes each. Signed-off-by: Arnd Bergmann <arnd@arndb.de> Link: https://lore.kernel.org/r/20200107200610.3482901-1-arnd@arndb.de Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'Documentation/devicetree/bindings/slimbus')
0 files changed, 0 insertions, 0 deletions