diff options
| author | landley <landley@69ca8d6d-28ef-0310-b511-8ec308f3f277> | 2005-08-23 20:03:17 +0000 |
|---|---|---|
| committer | landley <landley@69ca8d6d-28ef-0310-b511-8ec308f3f277> | 2005-08-23 20:03:17 +0000 |
| commit | a88cad8bba2f790fbb5f65fed3441089ac796acf (patch) | |
| tree | 86f0ce2508401a710ac9fd0a3c4bf17b2cfa1210 /README | |
| parent | 82c045893751fd63299f97ca7dd61248d5668f10 (diff) | |
| download | busybox-w32-a88cad8bba2f790fbb5f65fed3441089ac796acf.tar.gz busybox-w32-a88cad8bba2f790fbb5f65fed3441089ac796acf.tar.bz2 busybox-w32-a88cad8bba2f790fbb5f65fed3441089ac796acf.zip | |
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...
git-svn-id: svn://busybox.net/trunk/busybox@11231 69ca8d6d-28ef-0310-b511-8ec308f3f277
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions