Travis Geiselbrecht 77fa084cd0 [warnings][gcc 11] Fix a few annoying out of bounds pointer warnings ...

It seems to be in the case of a string op against a raw address, the
compiler decides the destination object is 0 bytes long and throws a
particular warning. Work around it by not using memcpy in one case and
by disabling the warning in the other.

Both are fairly benign code that basically operates in a hard coded way
that knows the destination buffer is valid.

2021-06-27 00:31:01 -07:00

..

loader.c

[warnings][gcc 11] Fix a few annoying out of bounds pointer warnings

2021-06-27 00:31:01 -07:00

rules.mk

[warnings][gcc 11] Fix a few annoying out of bounds pointer warnings

2021-06-27 00:31:01 -07:00