yf13 commented on issue #17443:
URL: https://github.com/apache/nuttx/issues/17443#issuecomment-3624520885
Here I tried on my local master branch (with last commit on Jul 30th) and
nuttx ELF got built with both Ubuntu stock arm-none-eabi-gcc v10.3.1 and a
custom built arm-none-eabi-gcc v13.2.1.
Build logs with custom toolchain v13.2.1:
```sh
$ arm-none-eabi-gcc -v
Using built-in specs.
COLLECT_GCC=arm-none-eabi-gcc
COLLECT_LTO_WRAPPER=/home/yf/.../prebuilts/gcc/linux-x86_64/arm-none-eabi/bin/../libexec/gcc/arm-none-eabi/13.2.1/lto-wrapper
Target: arm-none-eabi
Thread model: single
Supported LTO compression algorithms: zlib
gcc version 13.2.1 20231009 (Arm GNU Toolchain 13.2.rel1 (Build arm-13.7))
$ make -j4
CC: ctype/lib_iscntrl.c mtd/at24xx.c:135:4: warning: #warning "Assuming MTD
driver block size is the same as the FLASH page size" [-Wcpp]
135 | # warning "Assuming MTD driver block size is the same as the FLASH
page size"
| ^~~~~~~
CC: dirent/lib_dirfd.c chip/sam_start.c: In function 'sam_tcmenable':
chip/sam_start.c:109:2: warning: #warning Missing logic [-Wcpp]
109 | #warning Missing logic
| ^~~~~~~
CC: dlfcn/lib_dlfind_object.c chip/sam_clockconfig.c: In function
'sam_enabledefaultmaster':
chip/sam_clockconfig.c:303:2: warning: #warning REVISIT [-Wcpp]
303 | #warning REVISIT
| ^~~~~~~
CC: mm_heap/mm_heapmember.c chip/sam_xdmac.c: In function 'sam_physramaddr':
chip/sam_xdmac.c:444:2: warning: #warning REVISIT -- Do DCTM address need to
be remapped for DMA? [-Wcpp]
444 | #warning REVISIT -- Do DCTM address need to be remapped for DMA?
| ^~~~~~~
chip/sam_xdmac.c: In function 'sam_virtramaddr':
chip/sam_xdmac.c:450:2: warning: #warning REVISIT -- Do DCTM address need to
be remapped for DMA? [-Wcpp]
450 | #warning REVISIT -- Do DCTM address need to be remapped for DMA?
| ^~~~~~~
CPP: /tmp/nuttx/boards/arm/samv7/same70-xplained/scripts/flash.ld->
/tmp/nuttx/LD: nuttx
lto-wrapper: warning: Extra option to '-Xassembler': -mthumb, dropping all
'-Xassembler' and '-Wa' options.
lto-wrapper: warning: using serial compilation of 2 LTRANS jobs
lto-wrapper: note: see the '-flto' option documentation for more information
Memory region Used Size Region Size %age Used
flash: 47664 B 128 KB 36.36%
sram: 22152 B 384 KB 5.63%
CP: nuttx.bin
```
Built screen log with Ubuntu stock toolchain v10.3.1:
```sh
$ arm-none-eabi-gcc -v
Using built-in specs.
COLLECT_GCC=arm-none-eabi-gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-none-eabi/10.3.1/lto-wrapper
Target: arm-none-eabi
Thread model: single
Supported LTO compression algorithms: zlib
gcc version 10.3.1 20210621 (release) (15:10.3-2021.07-4)
$ make -j4
CC: mtd/at25.c mtd/at24xx.c:135:4: warning: #warning "Assuming MTD driver
block size is the same as the FLASH page size" [-Wcpp]
135 | # warning "Assuming MTD driver block size is the same as the FLASH
page size"
| ^~~~~~~
CC: fixedmath/lib_ubsqrt.c chip/sam_start.c: In function 'sam_tcmenable':
chip/sam_start.c:109:2: warning: #warning Missing logic [-Wcpp]
109 | #warning Missing logic
| ^~~~~~~
CC: grp/lib_getgrgidr.c chip/sam_clockconfig.c: In function
'sam_enabledefaultmaster':
chip/sam_clockconfig.c:303:2: warning: #warning REVISIT [-Wcpp]
303 | #warning REVISIT
| ^~~~~~~
CC: sched/sched_processtimer.c chip/sam_xdmac.c: In function
'sam_physramaddr':
chip/sam_xdmac.c:444:2: warning: #warning REVISIT -- Do DCTM address need to
be remapped for DMA? [-Wcpp]
444 | #warning REVISIT -- Do DCTM address need to be remapped for DMA?
| ^~~~~~~
chip/sam_xdmac.c: In function 'sam_virtramaddr':
chip/sam_xdmac.c:450:2: warning: #warning REVISIT -- Do DCTM address need to
be remapped for DMA? [-Wcpp]
450 | #warning REVISIT -- Do DCTM address need to be remapped for DMA?
| ^~~~~~~
CPP: /tmp/nuttx/boards/arm/samv7/same70-xplained/scripts/flash.ld->
/tmp/nuttx/LD: nuttx
lto-wrapper: warning: Extra option to -Xassembler: -mthumb, dropping all
-Xassembler and -Wa options.
CP: nuttx.bin
```
Will find and try toolchain 15.2 later.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
