-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Makefile.include: Generate lst file using objdump #19745
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sure looks handy
35a9470
to
25ff582
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ack
ping |
bors merge |
19745: Makefile.include: Generate lst file using objdump r=maribu a=nandojve ### Contribution description The MAP file does not provide all information necessary to do a full analize of generated code. This automatically generate the LST file with all relavant C and ASM code to help inspect code generated. ### Testing procedure This was tested using AVR and Cortex-M toolchains. Co-authored-by: Gerson Fernando Budke <[email protected]>
Build failed: |
25ff582
to
5881cf4
Compare
There is an issue with objdump for xtensa. It stay on a infinite loop generating the LST file. |
Hi @maribu , can you try again if the change is fine? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. I assume that the objdump call can have some impact on the CI time and won't be useful there, so let's only create it in local builds.
Please squash right away and feel free to kick bors afterwards
The MAP file does not provide all information necessary to do a full analize of generated code. This automatically generate the LST file with all relavant C and ASM code to help inspect code generated. Signed-off-by: Gerson Fernando Budke <[email protected]>
5881cf4
to
ae61702
Compare
bors merge |
Build succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page. |
19797: Makefile.include: don't use target lstfile implicitly r=maribu a=gschorcht ### Contribution description This PR reverts a part of PR #19745. It removes the `$(LSTFILE)` from the `BUILD_FILES` variable so that the `.lst` file isn't generated implicitly. If the `.lst` file is needed, it can be generated with `lstfile` target. **Background** The compilation time increased a lot with PR #19745. The reason is that the generation of the `.lst` file seems to be time-consuming. For example, on an Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz` with 8 cores and a SSD, it takes about 15 seconds for a complex application such as `tests/sys/usbus_msc` for a STM32F7 MCU. Therefore, the compilation time for ``` BOARD=stm32f723e-disco make -j8 -C tests/sys/usbus_msc ``` increased from about 1 sec to about 16 seconds (all source files were already compiled). Even for a small application ``` BOARD=stm32f723e-disco make -j8 -C tests/sys/shell ``` the compilation time increased from about 1 sec to about 10 seconds. ### Testing procedure Green CI ### Issues/PRs references Co-authored-by: Gunar Schorcht <[email protected]>
Contribution description
The MAP file does not provide all information necessary to do a full analize of generated code. This automatically generate the LST file with all relavant C and ASM code to help inspect code generated.
Testing procedure
This was tested using AVR and Cortex-M toolchains.