https://bugs.documentfoundation.org/show_bug.cgi?id=163441

ady <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|24.8.2.1 release            |6.1.6.3 release
                 CC|                            |ilmari.lauhakangas@libreoff
                   |                            |ice.org,
                   |                            |[email protected]
           Hardware|x86 (IA32)                  |All

--- Comment #13 from ady <[email protected]> ---
Partial recalculation failure as described in this report started in LO 6.1.

In LO 6.0.4.2, simple recalculate updates all values.

In LO 6.1.6.3, some values are not recalculated.

In both versions,
org.openoffice.Office.Calc.Formula.Calculation.OpenCLMinimumData is 100 by
default.

However, some recalculate issues have been resolved after LO 6.1 (e.g.
tdf#150766, tdf#137248, so LO 7.0 to LO 7.5), and therefore I cannot be sure
whether the current problem (25.2 alpha) is exactly the same as in LO 6.1,
making the bisection procedure somewhat tricky.

I am changing the Version field to 6.1, with the caveate I just mentioned.


STR:

0. Calc with OpenCL enabled.
1. Open attachment 197055 (AutoCalculate is enabled).
2. Focus (click once) on cell G102.
3. Press F9 key (recalculate).
3.1. Note that cell G104 recalculates (no longer equals 100), but the result is
only "partially correct" - please allow me such strange expression - because
other cells in the range E102:G103 (except G102) do not recalculate.

Hard Recalculate does not exist yet in LO 6.1, so disabling and re-enabling
AutoCalculate is needed in order to see _all_ cells recalculated. When Hard
Recalculate is available, it updates _all_ cells.

As mentioned before, whatever triggers this behavior (intentionally or not), it
depends on OpenCL being enabled in LO (at least in current versions, in which
the second older "Software Interpreter" option for OpenCL is no longer
available).

I do not know whether the behavior is intentional or not. Perhaps the behavior
is a consequence of performance improvements, and the reason for Hard
Recalculate to exist (i.e. maybe not really a bug).

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to