Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IOTCORE-389 - bring back legacy alignment for Arm C6 #8012

Merged
merged 1 commit into from
Sep 6, 2018

Conversation

JanneKiiskila
Copy link
Contributor

Description

Quite a few of the scatter files are not (yet) aligned to 8-byte
boundaries and therefore the removal of legacy alignment feature
(which is under deprecation warning, but it actually not YET
deprecated) broke quite a few builds to this error:

Error: L6244E: Exec region RW_IRAM1 address (0x200001ac) not aligned on a 8 byte boundary.

We must bring this option now back to fix the builds.

This option to ld (--legacyalign) can only be removed once all of
the scatter files have been fixed.

Pull request type

[x] Fix
[ ] Refactor
[ ] Target update
[ ] Functionality change
[ ] Breaking change

Quite a few of the scatter files are not (yet) aligned to 8-byte
boundaries and therefore the removal of legacy alignment feature
(which is under deprecation warning, but it actually not YET
deprecated) broke quite a few builds to this error:

Error: L6244E: Exec region RW_IRAM1 address (0x200001ac) not aligned on a 8 byte boundary.

We must bring this option now back to fix the builds.

This option to ld (--legacyalign) can only be removed once all of
the scatter files have been fixed.
@JanneKiiskila
Copy link
Contributor Author

@0xc0170 @adbridge @kjbracey-arm - this needs to get in ASAP, please. To next Mbed OS 5.10 RC.

@cmonr
Copy link
Contributor

cmonr commented Sep 6, 2018

@JanneKiiskila In the future, you can simply use @ARMmbed/mbed-os-maintainers as a shorthand.

/morph build

@mbed-ci
Copy link

mbed-ci commented Sep 6, 2018

Build : SUCCESS

Build number : 3018
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/8012/

Triggering tests

/morph test
/morph export-build
/morph mbed2-build

@mbed-ci
Copy link

mbed-ci commented Sep 6, 2018

@mbed-ci
Copy link

mbed-ci commented Sep 6, 2018

@0xc0170
Copy link
Contributor

0xc0170 commented Sep 6, 2018

/morph export-build

@c1728p9
Copy link
Contributor

c1728p9 commented Sep 6, 2018

Thanks for the fix @JanneKiiskila. @cmonr and @studavekar can we expand ARMC6 CI testing to build all boards so we can catch regressions like this?

@mbed-ci
Copy link

mbed-ci commented Sep 6, 2018

@0xc0170 0xc0170 merged commit 5d2f394 into ARMmbed:master Sep 6, 2018
@JanneKiiskila JanneKiiskila deleted the armc6-align-fix branch September 6, 2018 13:35
@JanneKiiskila
Copy link
Contributor Author

Thanks.

@andrewc-arm
Copy link
Contributor

andrewc-arm commented Dec 6, 2019

Hi,
I weaved through the code and finally found this issue while I am trying to solve this issue from my partner.
My research showed that legacyalign removes the padding to reduce more space.
http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0803g/pge1362075504330.html

Using --legacyalign, the linker assumes execution regions and load regions to be four-byte aligned. This option enables the linker to minimize the amount of padding that it inserts into the image.

But this issue is saying that there is a misalignment and we want to reduce padding via adding legacyalign. Does it make sense? I thought it should be other way around isn't it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants