Apache OpenOffice (AOO) Bugzilla – Issue 57790
Excel import: numbers are all wrong in imported file
Last modified: 2013-08-07 15:13:21 UTC
Importing the attached file results in a document with numbers that are virtually all incorrect (shown as zero, actually parsed by OO.o as very small numbers). The original file was exported from QuickBooks; I've then opened it in Excel to clean up names for submitting the file to the bug database. Opening in Excel (or even in OO.o 1.1.x!) will show you what the numbers ought to look like. This is a frustrating regression.
Created attachment 31416 [details] QuickBooks-exported file containing a monthly budget report
Hi, could not reproduce. There did you get your OOo2.0 from ? What Linux distribution do you use ? Frank
I'm using OO.o 2.0 built from source on Gentoo Linux in order to get KDE integration on the desktop. CFLAGS="-march=athlon-xp -O2 -pipe -mmmx -msse -m3dnow" gcc (GCC) 3.3.6 (Gentoo 3.3.6, ssp-3.3.6-1.0, pie-8.7.8)
This looks like a Gentoo compilation flags problem, maybe related to optimization. Try whether compiling sc/source/filter/excel/xltools.cxx with -O1 instead of -O2 helps. If not, try if it does compiling the entire directory sc/source/filter/excel/ with -O1, or the entire sc module or ... If nothing helps, use the official build downloaded from one of the OOo mirrors, that should do.
Instead of -O1 you can also try to add -fno-strict-aliasing to the compiler flags, may be sufficient. Strict-aliasing is disabled in O1, but enabled in all other optimizations.
Thanks -- your suggestion to add -fno-strict-aliasing did the trick. Will you consider adding this somehow to the appropriate makefiles, or should I perhaps open a bug with Gentoo to invite them to make sure this flag is used in builds of OO.o from source?
The attached patch should solve the problem regardless of the optimization settings.
Created attachment 31581 [details] patch
Anyway, this is most certainly not the only problematic code place regarding optimization. The original OOo build environment currently only uses -O1, which is different from just disabling the strict-aliasing, so Gentoo should force -O1 too.
oops.. the -O1 was some time ago.. currently, for OOo2.0 it is -Os -fno-strict-aliasing, so this is what Gentoo should force.
Hi Daniel, yours as dicussed onthe phone. Frank
started
fixed in SRC680/dr46 (OOo 2.0.3)
back to QA no change of functionality, just check import of numbers in Excel files re-open issue and reassign to oc@openoffice.org
reassign to oc@openoffice.org
reset resolution to FIXED
verified in internal build cws_dr46
closed because fix available in OpenOffice.org Developer Snapshot Build src680_m167