Repository navigation
[BUG][CI][CHT][BYT] Build failure on CHT: .text will not fit in region sof_text_start #3063
Description
[100%] Linking C executable sof
/home/test/xcc/install/tools/RD-2012.5-linux/XtensaTools/bin/xt-ld: sof section .text' will not fit in region sof_text_start'
CMakeFiles/sof.dir/build.make:1820: recipe for target 'sof' failed
make[3]: *** [sof] Error 2
CMakeFiles/Makefile2:396: recipe for target 'CMakeFiles/sof.dir/all' failed
make[2]: *** [CMakeFiles/sof.dir/all] Error 2
CMakeFiles/Makefile2:1658: recipe for target 'src/arch/xtensa/CMakeFiles/bin.dir/rule' failed
make[1]: *** [src/arch/xtensa/CMakeFiles/bin.dir/rule] Error 2
Makefile:723: recipe for target 'bin' failed
make: *** [bin] Error 2
Activity
ClarexZhou commentedon Jun 18, 2020
Bi-sect result: issue occurred from a2d1e1e
ClarexZhou commentedon Jun 18, 2020
@bkokoszx could you please help to check first?
xiulipan commentedon Jun 22, 2020
The TEXT size on CHT is just a little out range.
After hack with memory.h, we can got the current TEXT size.
marc-hb commentedon Jun 24, 2020
Yet everything is green in PR #2897 ?!
@xiulipan do you think this went over the limit only when PR #2897 was rebased and combined on top of some other code addition?
In an ideal world with infinite resources, CI is run on each PR twice: before and after rebase. In the real world projects generally choose one or the other.
[-][BUG][CI][CHT] Build failure on CHT: .text will not fit in region sof_text_start[/-][+][BUG][CI][CHT][BYT] Build failure on CHT: .text will not fit in region sof_text_start[/+]xiulipan commentedon Jun 29, 2020
@marc-hb Yes, this is the issue with merge.
When #2897 run with test, it would be on code base A.
But when it is merged, it would be on code base B. I manually test with base A and B and the issue is there.
That would be an ideal solution, but the question here is you will never know what is the point for the rebase. The rebase happen when you click the merge button. At that time, the PR is merged into the master branch.
We indeed have some after merge check. In both Jenkins and Travis. But we only have feedback from Travis and internal warning message in Jenkins. Will try to make the Jenkins push check expose to GitHub. (internal issue 498)
marc-hb commentedon Jul 15, 2020
Was this fixed by #3080 ? If yes please close.
aiChaoSONG commentedon Jul 15, 2020
colse for fixed by #3080