summaryrefslogtreecommitdiffstats
path: root/quantum/keymap_common.c
diff options
context:
space:
mode:
authorFred Sundvik <fsundvik@gmail.com>2017-04-09 20:00:42 +0200
committerFred Sundvik <fsundvik@gmail.com>2017-04-13 15:00:29 +0200
commit653580477663f527f322650f6d39824cdf6cddc0 (patch)
tree40d3d5a3fa6f15c8e6d7c47855a94e4ac79e0403 /quantum/keymap_common.c
parenta4ef86034c328ed7db9b9f0e2e49c5019d5aabc8 (diff)
downloadqmk_firmware-653580477663f527f322650f6d39824cdf6cddc0.tar.gz
qmk_firmware-653580477663f527f322650f6d39824cdf6cddc0.tar.xz
Disable array bounds warning in keymap_function_id_to_action
Diffstat (limited to 'quantum/keymap_common.c')
-rw-r--r--quantum/keymap_common.c7
1 files changed, 7 insertions, 0 deletions
diff --git a/quantum/keymap_common.c b/quantum/keymap_common.c
index 6cf4f031f..9dafc8b51 100644
--- a/quantum/keymap_common.c
+++ b/quantum/keymap_common.c
@@ -179,5 +179,12 @@ uint16_t keymap_key_to_keycode(uint8_t layer, keypos_t key)
__attribute__ ((weak))
uint16_t keymap_function_id_to_action( uint16_t function_id )
{
+ // The compiler sees the empty (weak) fn_actions and generates a warning
+ // This function should not be called in that case, so the warning is too strict
+ // If this function is called however, the keymap should have overridden fn_actions, and then the compile
+ // is comparing against the wrong array
+ #pragma GCC diagnostic push
+ #pragma GCC diagnostic ignored "-Warray-bounds"
return pgm_read_word(&fn_actions[function_id]);
+ #pragma GCC diagnostic pop
}