libreoffice ftbfs on armhf
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libreoffice (Ubuntu) |
Fix Released
|
High
|
Jani Monoses | ||
Precise |
Fix Released
|
High
|
Jani Monoses |
Bug Description
in precise,
/bin/bash: line 1: 11191 Segmentation fault LD_LIBRARY_
dmake: Error code 139, while making 'runtest'
Retrying /build/
Making: all_bridgetest.
cd ../../unxlngr.
-ro uno_services.rdb -ro uno_types.rdb \
-s com.sun.
/bin/bash: line 1: 11210 Segmentation fault LD_LIBRARY_
dmake: Error code 139, while making 'runtest'
tags: | added: patch |
Changed in libreoffice (Ubuntu Precise): | |
assignee: | Björn Michaelsen (bjoern-michaelsen) → Michael Casadevall (mcasadevall) |
tags: | added: rls-mgr-p-tracking |
Changed in libreoffice (Ubuntu Precise): | |
assignee: | Michael Casadevall (mcasadevall) → Riku Voipio (riku-voipio) |
tags: |
added: rls-p-tracking removed: rls-mgr-p-tracking |
The ARM Procedure Call Standard document on http:// infocenter. arm.com/ has details of the VFP variant of the procedure call standard, required for armhf.
Simplified, each floating-point argument is allocated first to the VFP registers if there are some available (from s0-s15 / d0-d7), and then to the stack when there are no more VFP argument registers available.
Basically, for the armhf case we need:
* A separate array to track the values to be passed to the called function in floating-point registers
* A separate counter to track which floating-point argument registers have already been allocated
* Separate implementations of INSERT_FLOAT() and INSERT_DOUBLE() to allocate to VFP regs and then to the stack (similarly to the way the INSERT_INT*() macros work)
* Code to copy the required arguments into the VFP regs when the actual target function is called
* Code to handle floating-point return values (float/double returned VFP registers) -- refer to the Procedure Call Standard for exact details)