Re: Minimum.exe Text Size Outliers

Hello Joel, Am 26.05.21 um 22:47 schrieb Joel Sherrill: Another minimum size report. If the text size after subtracting the FDT blob is below 64K, the BSP is not in the report. The adjusted size is reported. It looks like some significant percentage of those over 64k are managing to pull in pri

Re: Minimum.exe Text Size Outliers

Another minimum size report. If the text size after subtracting the FDT blob is below 64K, the BSP is not in the report. The adjusted size is reported. It looks like some significant percentage of those over 64k are managing to pull in printf or something in the family. I wonder if we should ban p

Re: Minimum.exe Text Size Outliers

On 26/05/2021 19:23, Joel Sherrill wrote: On Wed, May 26, 2021 at 6:02 AM Sebastian Huber > wrote: On 25/05/2021 20:33, Christian Mauderer wrote: > >> >> I thought Sebastian added a "malloc" for the BSP to use before the >>

Re: Minimum.exe Text Size Outliers

On Wed, May 26, 2021 at 6:02 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 25/05/2021 20:33, Christian Mauderer wrote: > > > >> > >> I thought Sebastian added a "malloc" for the BSP to use before the > >> heap was initialized. But I don't remember the name. Am I remembering

Re: Minimum.exe Text Size Outliers

On 25/05/2021 20:33, Christian Mauderer wrote: I thought Sebastian added a "malloc" for the BSP to use before the heap was initialized. But I don't remember the name. Am I remembering correctly? I don't really know that malloc. But I doubt that it works that early. Again: Copying the FDT

Re: Minimum.exe Text Size Outliers

On Tue, May 25, 2021 at 1:57 PM Christian Mauderer wrote: > Hello Joel, > > missed the attachement. So if we leave out the ones with bsp_fdt_blob > and the ones that you marked with "FOUND close()" that leaves the > following ones (if I didn't miss any): > > === arm-nucleo-h743zi-mini

Re: Minimum.exe Text Size Outliers

Hello Joel, missed the attachement. So if we leave out the ones with bsp_fdt_blob and the ones that you marked with "FOUND close()" that leaves the following ones (if I didn't miss any): === arm-nucleo-h743zi-minimum.exe = === arm-stm32h7-minimum.exe =

Re: Minimum.exe Text Size Outliers

Hello Joel, On 25/05/2021 19:10, Joel Sherrill wrote: Thanks for the feedback. I did save all of the minimum.exe files as @CPU@-@b...@-minimum.exe so they could be analysed. For exe, I did a size, the tail -5,  and also looked for some symbols that are hints of dependency chains to things not

Re: Minimum.exe Text Size Outliers

Thanks for the feedback. I did save all of the minimum.exe files as @CPU@ -@b...@-minimum.exe so they could be analysed. For exe, I did a size, the tail -5, and also looked for some symbols that are hints of dependency chains to things not needed. close(), atexit(), and rtems_libio_post_driver() b

Re: Minimum.exe Text Size Outliers

Hello Joel, I think we currently have very few BSPs with a linked in device tree blob. I know only of the new imxrt (which isn't in your list) and I think one Xilinx something BSP. For imx: I only have a build for some minimum based on 5 at hand right now. I have to re-build an up to date ve

Minimum.exe Text Size Outliers

Hi I built all 187 BSPs overnight and saved minimum.exe. Although I think 64K is still too much code, I am using that as an initial cutoff when asking for some help in identifying why minimum.exe is surprisingly large for some BSPs. 146 stayed under 64k which leaves 41 needing some investigation o