Turn on OpenCL computing. Tools - Options - LibreOffice Calc - Formula - Detailed Calculation Settings - Custom - Details... - Enable OpenCL for some formula computation: True In A1 enter 'aaaa'. In B1 enter '=A1'. B1 will contain 'aaaa'. Now enter 'bbbb' in A2. In B2 enter '=A2'. B1 and B2 will contain '#NULL'.
My OpenCL driver is 'Internal, software interpreter'.
Hey Andras. The Internal, software interpreter is not an OpenCL device/driver. It is a internal version for testing and might sadly still expose some bugs. If you want to test the OpenCL driver and don't have a suitable graphics driver you can use the AMD OpenCL SDk which works with any CPU.
*** Bug 76167 has been marked as a duplicate of this bug. ***
Confirmed by duplicate.
Yup. This is a known issue. It started doing it all of a sudden, and I haven't come around to look into it yet.
I believe this was caused by the earlier implementation of kernel precompilation. We decided to disable that later, so the latest version shouldn't do this anymore.
(In reply to comment #6) > I believe this was caused by the earlier implementation of kernel > precompilation. We decided to disable that later, so the latest version > shouldn't do this anymore. Yes, current build from libreoffice-4-2 does not do it any more. It exhibits a different bug now. :) In A1 enter 'aaaa'. In B1 enter '=A1'. B1 will contain 'aaaa'. Now enter 'bbbb' in A2. In B2 enter '=A2'. B1 and B2 will contain 'AAAA' and 'BBBB' respectively.
That's currently by design, unfortunate it may be. String handling with OpenCL backend is extremely limited.
Let us remove the regression keyword as it is related to a new feature.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (4.4.1 or later): https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-07-18
*** Bug 99753 has been marked as a duplicate of this bug. ***
It seems that the setting described here is an addition since this bug report: https://bugs.documentfoundation.org/show_bug.cgi?id=99753#c20 You have to have at least as many references as set as minimum data size for OpenCL here: 'Tools -> Options... -> LibreOffice Calc -> Formula -> Detailed Calculation Settings -> Custom -> OpenCL Settings -> Minimum data size for OpenCL use' (100 by default) If that's met, the bug still occurs in current master build.
Kohei, the issue is in sc/source/core/data/column2.cxx. I'd point to [1] in this case, but there are a couple of other getDataIgnoreCase() in calls that might also be relevant. [1] (*rColArray.mpStrArray)[nPos] = itData->getDataIgnoreCase(); http://opengrok.libreoffice.org/xref/core/sc/source/core/data/column2.cxx#2340
*** Bug 99854 has been marked as a duplicate of this bug. ***
Can the original problem really be reproduced? (With more than 100 copies of the rows.) If not, surely this should be resolved, instead of being kept open without any clear description of what the actual bug is. The intent has definitely been for quite some time that nothing using strings should go through OpenCL at all any longer. The OpenCL implementation of string stuff was indeed fairly broken, one thing indeed being that strings were uppercased at some stage.
The issue described in Comment 7 can be reproduced. See it described with specific steps in duplicate report bug 99753, comments 17 and 21 (though the steps described in Comment 7 here is equally adequate knowing it's related to the Software Interpreter, which is implied in Comment 1).
Note that the "software interpreter" thing was VERY DIFFERENT back in early 2014 than what it is to-day. It is fairly useless to draw too many conclusions about about thew current code-base from comments from 2014.
Ah! Indeed, now I can reproduce. So it is the infamous "software interpreter" indeed. (And not OpenCL.) Sigh... Editing the bug title to match reality, there is no such thing as an "OpenCL interpreter" in LibreOffice. "cell group interpreter" would be more correct. But sure, let's just call it "software interpreter".
I mean "formula group", not "cell group", sorry. "Formula group" is the term used in the code.
Created attachment 125959 [details] Bugdoc It is of course trivial and fast to construct a reproducing document manually, but anyway here is also a ready-made such document, for completeness.
Suggested patch at https://gerrit.libreoffice.org/#/c/26729/ . But I am a bit scared to approve it. Will it break something else instead?
Tor Lillqvist committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=f948dce856d51704e1962553198015dbebb6e527 tdf#75387: Don't case-fold strings for formula group calculations It will be available in 5.3.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Looked harder and am now fairly convinced that the patch will not break anything else. Patch is in master, awaiting review in Gerrit for 5.2 and 5.1. Resolving as fixed.
Tor Lillqvist committed a patch related to this issue. It has been pushed to "libreoffice-5-1": http://cgit.freedesktop.org/libreoffice/core/commit/?id=593d8c825df9c0e79b2a8bb9a726ffb34b146845&h=libreoffice-5-1 tdf#75387: Don't case-fold strings for formula group calculations It will be available in 5.1.5. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Tor Lillqvist committed a patch related to this issue. It has been pushed to "libreoffice-5-2": http://cgit.freedesktop.org/libreoffice/core/commit/?id=6fd975b1f6aca9fd26a202b4997a0485e1b8de46&h=libreoffice-5-2 tdf#75387: Don't case-fold strings for formula group calculations It will be available in 5.2.0.2. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
*** Bug 100803 has been marked as a duplicate of this bug. ***
*** Bug 102079 has been marked as a duplicate of this bug. ***