This is an archive of the discontinued LLVM Phabricator instance.

[lbc++abi] [unwinder] Support Cortex-m0
ClosedPublic

Authored by jroelofs on Sep 11 2014, 2:04 PM.

Details

Reviewers
rengolin
compnerd
Summary

Also has a pair of fixes for armv4t. Let me know if you'd like those in a separate patch.

Diff Detail

Event Timeline

jroelofs updated this revision to Diff 13601.Sep 11 2014, 2:04 PM
jroelofs retitled this revision from to [lbc++abi] [unwinder] Support Cortex-m0.
jroelofs updated this object.
jroelofs edited the test plan for this revision. (Show Details)
jroelofs added reviewers: rengolin, compnerd.
jroelofs added a subscriber: Unknown Object (MLST).
jroelofs updated this revision to Diff 13602.Sep 11 2014, 2:05 PM

[Same patch, better diff]

compnerd added inline comments.Sep 11 2014, 7:12 PM
src/Unwind/UnwindRegistersSave.S
335

Doesn't this change the behavior for __ARM_ARCH >= 7?

352

Doesn't this change the behavior for __ARM_ARCH >= 7?

368

This also doesn't work for ARMv7. Consider ARM VFPv3-d16 (e.g. Tegra2) ... vstmia r0, {d16-d31} refers to a non-existent register set.

392

Do all CPUs have the wmmxt register set? It might be more prudent to move this out into a separate translation unit that is linked in if the target supports iwmmxt.

419

Oh joy ... this is scary.

Do we have some guarantee that they won't accidentally use long rather than int?

420

Similar to above.

rengolin added inline comments.Sep 12 2014, 4:19 AM
src/Unwind/UnwindRegistersRestore.S
341

I think we should use the same trick we used in other ARM files, to define a macro that is set by the arch for returning.

355

Do you want to export the symbols (unwindVFP) but have it do nothing? Is it even possible to try to unwind VFP on v6M? Shouldn't this be a compilation error?

380

This macro is in a different order than the one above, and will generate vldmia on v6M which will fail.

src/Unwind/UnwindRegistersSave.S
285

Maybe we should also have a macro that will use thumb on thumb-only platforms like v6M and v6M variants. That would have to be accompanied by changes to other areas, making them Thumb/2 friendly (like the ones you add here).

368

And this is exactly the opposite as the other, which would just get "bx lr" on ARMv6M

Sorry about the hideously bad merge....

src/Unwind/UnwindRegistersRestore.S
341

Sounds like a good idea to me.

355

I think that this will never get called on v6m because it doesn't have vfp registers, so the compiler will never issue the unwind opcodes that trigger this being called. Maybe that warrants having the body be:

assert(false)

?

This could be completely ifdef'd out on v6m, but that would mean ifdefing out the callers too, which would be a bit ugly. It does save a few bytes though....

380

Oops, bad merge. Yeah, they should be transposed.

397

Another bad merge. Transpose this with the line above it.

440

Another bad merge / patch cut. I didn't intend to include the s/MMXControlEPj/MMXControlEPm/ change.

src/Unwind/UnwindRegistersSave.S
285

like a LIBUNWIND_THUMB_ONLY flag?

335

Another bad merge. This line, and the one above it should be transposed.

352

Another bad merge. This line, and the one above it should be transposed.

368

Conditions on this one should be flipped.... oops.

382

Maybe this should use that RETURN macro @rengolin suggests?

392

I think the idea here (before my change) was that if you were to build this library with -march=armv5t then you could either link it with code for a PXA270 and get something that would work on that arch, or link it with normal v5t code and get something that would work on a vanilla v5t board.

With my change I am trying to be conservative... I don't know whether there are any v6m's with iwmmx support, but if there are, then this should DTRT.

419

Oops, another bad patch cut. The s/saveiWMMXControlEPj/saveiWMMXControlEPm/ change is part of a different patch where I change the type of the argument to void*.

jroelofs updated this revision to Diff 13719.Sep 15 2014, 10:50 AM

Move return instructions into ARM_RETURN macro.
Add ARM_THUMB1_ONLY guard.
Add ARM_HAS_NO_VFP guard.

jroelofs updated this revision to Diff 13720.Sep 15 2014, 10:52 AM

Forgot an #endif. Sorry about the spam.

compnerd requested changes to this revision.Sep 15 2014, 6:22 PM
compnerd edited edge metadata.

Please drop ARM_RETURN and use JMP(lr). That is duplicating an existing macro which is already in use.

Im not sure I understand why you are creating a new macro for the thumb check. __ARM_ARCH_ISA_THUMB == 1 is sufficient to identify if you only have Thumb-1. However, do you really want to use thumb instructions if you only have Thumb-1?

I dont understand the need for the ARM_HAS_NO_VFP. Isn't __VFP_FP__ usable for your check there? I don't think we need yet another macro, particularly if there is one that is defined by the compiler.

Finally, is __ARM_WMMX supposed to be defined for ARMv6M/s?

This revision now requires changes to proceed.Sep 15 2014, 6:22 PM
In D5314#14, @compnerd wrote:

Please drop ARM_RETURN and use JMP(lr). That is duplicating an existing macro which is already in use.

Sure, I'll copy over the ARM part of compiler_rt's assembly.h

Im not sure I understand why you are creating a new macro for the thumb check. __ARM_ARCH_ISA_THUMB == 1 is sufficient to identify if you only have Thumb-1. However, do you really want to use thumb instructions if you only have Thumb-1?

Sorry, bad name. What I meant here is to have a macro that means "doesn't have the ARM instruction set" (i.e. v6m, v6sm, v7m). I think this is what I actually mean:

#if !defined(__ARM_ARCH_ISA_ARM)

I dont understand the need for the ARM_HAS_NO_VFP. Isn't __VFP_FP__ usable for your check there? I don't think we need yet another macro, particularly if there is one that is defined by the compiler.

No, __VFP_FP__ isn't the right one for this. The best reference I can find for what that one means is this: https://wiki.debian.org/ArmEabiPort "Note that __VFP_FP__ does not mean that VFP code generation has been selected. It only speaks of the floating point data format in use and is normally set when soft-float has been selected."

After some digging around in http://infocenter.arm.com/help/topic/com.arm.doc.ihi0053c/IHI0053C_acle_2_0.pdf I think __ARM_FP is the right one to use, but it looks like clang doesn't ever define that one on 32bit arm. I should probably fix that first....

Finally, is __ARM_WMMX supposed to be defined for ARMv6M/s?

I don't know of any v6m/v6sm's with iWMMX instructions (and therefore __ARM_WMMX), but it might be possible that could exist, hence the:

#if (!defined(__ARM_ARCH_6M__) && !defined(__ARM_ARCH_6SM__)) || __ARM_WMMX

My assembler barfs on the coprocessor instructions in those blocks, so maybe it's not possible to have iWMMX instructions on a v6m part?

jroelofs updated this revision to Diff 13753.Sep 16 2014, 8:35 AM
jroelofs edited edge metadata.

Address a few of @compnerd's comments. This is contingent on fixing __ARM_FP in clang.

compnerd added inline comments.Sep 17 2014, 8:05 AM
assembly.h
65 ↗(On Diff #13753)

The whole block of __ARM_ARCH seems incorrect to me. What compiler are you trying to support? Both clang and gcc have supported this part of the ACLE for some time now.

jroelofs updated this revision to Diff 13990.Sep 23 2014, 7:01 AM
jroelofs edited edge metadata.

Dump the __ARM_ARCH ACLE shims that were copy-pasted from compiler_rt's assembly.h (and have been deleted there).

rengolin accepted this revision.Sep 24 2014, 3:16 AM
rengolin edited edge metadata.

Hi Jon,

Looks ok to me, but please wait for Saleem's blessing.

cheers,
--renato

compnerd accepted this revision.Oct 1 2014, 9:32 PM
compnerd edited edge metadata.

Thanks for making all the adjustments!

This revision is now accepted and ready to land.Oct 1 2014, 9:32 PM
jroelofs closed this revision.Oct 2 2014, 6:36 AM

Thanks for the review! Committed as r218869.

Jon