riscv-rt patch: remove references to eh_frame

[romancardenas]

This PR serves to give me permission to publish a v0.13.1 patch fr riscv-rt. This release cherry-picks a commit that is already in master, but remains still unpublished.

Note that, if accepted, I will publish the patch from the rvrt-patch branch, not master.

Closes #260

[rmsyn]

Note that, if accepted, I will publish the patch from the rvrt-patch branch, not master.

Why do you prefer publishing from rvrt-patch instead of master?

Otherwise, this LGTM.

[romancardenas]

We can either wait and do a "major" release including riscv or release this patch ASAP and do the major release later. Whatever you prefer

[rmsyn]

We can either wait and do a "major" release including riscv or release this patch ASAP and do the major release later. Whatever you prefer

Maybe we can bring it up at tomorrow's meeting?

I think if we're doing a release with riscv also, maybe it could wait until we're ready for the next release we're working on? Especially since users who need it now can track the master branch.

Doing a patch release only for riscv-rt makes more sense to me, if we want to publish a release to crates.io now.

Would definitely like to get more feedback from others in the working group.

[romancardenas]

I guess it also depends on how long will it take to have the next version of riscv ready. I think the only blocker is #229 right?

[rmsyn]

I think the only blocker is #229 right?

If that is the only blocker, I can try to finish the final few registers by the end of the week.

[romancardenas]

OK, let's do that. We will wait a bit and release a new version of all the riscv packages once we are done with #229.