StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17651921
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-07-15T10:20:45.877
FavoriteCount
0
LastActivityDate
2013-07-15T10:20:45.877
LastEditDate
LastEditorUserId
0
OwnerUserId
2158495
ParentId
17637445
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
It is not clear which assembly goes wrong as both are marked as 'declare the array <code>m[5]</code> as <code>double m[5]</code>' and unfortunately I don't have the hardware nor the cross-compiler to reproduce your problem. Remarkably the loops in both assembly codes are very similar. The only difference being that <code>v</code> is located in <code>d16</code> in the first and in <code>d8</code> in the second. The <code>v</code> that is passed to the <code>printf</code> is located in <code>(r5,r6)</code> in both loops and correctly copied to <code>(r2,r3)</code> before calling <code>printf</code>. For variadic functions the floating point registers shall not be used to pass parameters, contrary to non-variadic functions. Thus both loops look correct. The only explanation I can think of is a mismatch in the ABI used for the compiled code and the ABI of the library containing <code>printf</code>. Especially considering that the compiled code comes from a cross compiler and I'm assuming the <code>printf</code> comes from a dynamic library on the system. As the <code>printf</code> is called conforming to the EABI for ARM, I think the bug is in the <code>printf</code> of the library. If your cross compiler allows static linking, you may try that as you will be using a library that corresponds with the compiler. Of course the application becomes bigger, but it could at least confirm suspicion on the implementation of the <code>printf</code>. You may want to check if the library is compiled with an EABI complying compiler. If you can step through the <code>printf</code> on a debugger on the iPad, then you should be able to determine where the <code>printf</code> is taking its floating point parameter from. It should take it from <code>(r2,r3)</code>. Unfortunately I can not give a conclusive answer, but I hope my pointers for further investigation are helpful.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POThis maybe a bug of llvm-gcc for ios-armv7, that I can't explain
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USBryan Olivier
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.