Much less memory footprint & better scalability.

Change-Id: Idef9afe5fa6e247e59fb949d4c9955fab4f669dc

Change-Id: I2bbfa48e49bb8c91c6d3e2bb485ded9e8e67f13b

Change-Id: I698e70e7713697e2951c3e6ead4b4d2198d8a6cf

This speeds up the process considerably if the size of the trailing
empty rows is huge.

Change-Id: Ide91174b09472a20309b4f6e18d658cb8fbefa42

Change-Id: I47632b7ae93f4e68c4512fc30f4e4fe18e1c5f4d

Change-Id: I8cbf348289acb98d30d8e295f296c43655b00a08

Change-Id: I1fa81b32f9ffc70769876becbcf213796cab405b

Change-Id: I1ba3278d8c74c62f28f2b89bec35bc33be477094

Change-Id: If90c068eb4db26203612a54aa3536118650bfb43

Change-Id: Idb9839c827729edaa72442f78fbd2fd6561d95c8

Change-Id: I0461b7a23b4743f6e73e6c771b1b2119ad1bce15

Change-Id: Idca4dab27644e2c30a6c0a7549021c59fd99bc3a

Change-Id: I9aab3ec39b833dac242b9ede21ac3f2e5eb78200

Change-Id: I0604998e5019757c47050e4f94b1feb1b847cfca

Change-Id: I4ec1a8225ae3c84352643876065fb4cc7073b9f4

Change-Id: I42d31f6653990a81eff815d3d0feffad84b1379e

...rather than a general RuntimeException, for consistency with existing service
ctor code.

Change-Id: Ia9ac14a1b5bcecb24394e7b9cade369f3f9303f0

Change-Id: I1b673e8ae1a8487feaa41d827664d06e7ea3aaaf

Change-Id: I14794ca0cd2a8ea84ba41e1dc689503647696e3a

Change-Id: Ia4cfd0b848408713cff4f476e6d6be069d1cb5a8

Change-Id: I1ff8508daa2863020c6d7fa735f0f23b1ce96d8f

This is such a fatal error that there is probably no point in trying to handle
it, so allow to simplify client code by removing the requirement to check for a
null return value.

Simplified some client code accordingly (modules configmgr and ure, and the code
generated by cppumaker and javamaker).

Change-Id: I51c0b270ec73409374f7439a47ee061407a46e31

Change-Id: I68a1f132d0c4c379a3bcbf5e1a0f9a37604a8948

Change-Id: I872dd578729d8fe43d50fbf835b977adff8aded5

Change-Id: Ib17e2153746da9e097cccef1bd70bbbd349c7920

Change-Id: I9d1d21737da21724f98c2a7d06734693bb4ebedb

Change-Id: I0e6992afbeffaf3b993e6630fb396d93012890e0
Reviewed-on: https://gerrit.libreoffice.org/632Tested-by: Norbert Thiebaud <nthiebaud@gmail.com>
Reviewed-by: Norbert Thiebaud <nthiebaud@gmail.com>

Change-Id: Ib958807b0227d6aa7fdd0c51b2ad7a595f4eaa71

Change-Id: Id8f0d0eada854cc584e613b10e341602517ed47e
(cherry picked from commit 1c335df02a7ed77a571ffd5f51f5d6d6710d7d52)

Change-Id: I50ba7e12eec41c90dff1a378113f46bff36552a4

Change-Id: Iaccb9a09576e47ad35161f9ac5e4f07c192267d9

Change-Id: Ic4c4806ea3e791d0d75621e678166d0ffbbfa96a

Change-Id: I5f121cbeff3f0cda5776d5361e585eaa1b48ea63

Change-Id: I508ceb8dfe13fbfe54b4262d26bd215462c90c40

Change-Id: Id6a1f9f514c8221e5ca79e1eaafe69916fc1d1bd

Change-Id: I33fbe68b17e9a1c457b37c6d81619f2df67fbe8d

atomic increment/decrement is provided by
osl_increment/decrementInterlockedCount()
but that is a exported dll function, so it cannot be inlined.

valgrind analysis of a run, loading a medium sized spreadsheet, shows
that these 2 functions were called 3.5 millions times for a total cost of
55 millions of instructions... a cost of 8 instructions per call,
which is at least a 300% overhead since an atomic inc/dec is 2 instructions
iow we could save about 1% of the total instruction count of that run(4.6B)

We cannot change the existing api, as this would break ABI.
but we can add a new api. and migrate internal user to it.

osl_atomic_decrement/osl_atomic_increment do the same task,
than osl_*IntelockedCount() but do that inlined if possible.

Note that this version only optimize the case GCC with atomic built-in.
but support for other case should not be very hard.

follows-up patches will replace the use of the osl_*InterlockedCount()
in the product with their osl_atomic_* equivalent.

Change-Id: If4dcbf94ea6f62eb6d55d30613fe65878ffb8023
Signed-off-by: Stephan Bergmann <sbergman@redhat.com>