aboutsummaryrefslogtreecommitdiff
path: root/libbb/xgetlarg.c
diff options
context:
space:
mode:
authorRob Landley <rob@landley.net>2005-08-23 20:03:17 +0000
committerRob Landley <rob@landley.net>2005-08-23 20:03:17 +0000
commitf4c684a1efcf8a602d0803c889aba610b9a5ddb8 (patch)
tree86f0ce2508401a710ac9fd0a3c4bf17b2cfa1210 /libbb/xgetlarg.c
parent6417564eebe6b9591d9c001160d201194bd5e24a (diff)
downloadbusybox-f4c684a1efcf8a602d0803c889aba610b9a5ddb8.tar.gz
When compiling with FEATURE_MTAB_SUPPORT disabled, the call to erase_mtab()
can never be made because useMtab is initialized to 0, and all the other assignments of that variable assign 0 to it. Any compiler that can perform simple constant propogation on local variables will optimize away if statements testing against that variable, thus the call to erase_mtab() will never be made. When compiling for arm using gcc 3.3.3 with FEATURE_MTAB_SUPPORT disabled, the linker complains that it can't find erase_mtab(). The arm optimizer isn't exactly the brightest member of the family, and apparently needs to be hit over the head with a hammer to get its' attention...
Diffstat (limited to 'libbb/xgetlarg.c')
0 files changed, 0 insertions, 0 deletions