gh-raspberrypi/pico-sdk
Watch
1
0
Fork
You've already forked pico-sdk
 0
Code Issues 262 Pull requests 63 Releases Activity

provide slightly meaningless _start symbol for boot_stage2 to make LLVM lld happy #2080

Merged
kilograham merged 1 commit from clang_lld_warning into develop 2024-11-21 10:10:12 -06:00
Conversation 8 Commits 1 Files changed 2 +2
kilograham commented 2024-11-20 20:41:29 -06:00 (Migrated from github.com)

fixes #1813

fixes #1813
Wren6991 (Migrated from github.com) reviewed 2024-11-20 20:41:29 -06:00
will-v-pi (Migrated from github.com) reviewed 2024-11-20 20:41:29 -06:00
peterharperuk (Migrated from github.com) approved these changes 2024-11-21 05:22:10 -06:00
armandomontanez commented 2024-11-21 09:26:30 -06:00 (Migrated from github.com)

ENTRY(_stage2_boot) should do the trick and might have slightly more clear intent.

`ENTRY(_stage2_boot)` should do the trick and might have slightly more clear intent.
armandomontanez commented 2024-11-21 09:32:24 -06:00 (Migrated from github.com)

Also side note, I'm not seeing any declarations of an .entry section in the codebase, am I missing something or is that something that could be cleaned up?

Also side note, I'm not seeing any declarations of an `.entry` section in the codebase, am I missing something or is that something that could be cleaned up?
kilograham commented 2024-11-21 10:09:20 -06:00 (Migrated from github.com)

ENTRY(_stage2_boot) should do the trick and might have slightly more clear intent.

yeah, i thought about that, but there is no requirement to provide that symbol... we do always enter the image at the beginning

> `ENTRY(_stage2_boot)` should do the trick and might have slightly more clear intent. yeah, i thought about that, but there is no requirement to provide that symbol... we do always enter the image at the beginning
kilograham commented 2024-11-21 10:10:07 -06:00 (Migrated from github.com)

Also side note, I'm not seeing any declarations of an .entry section in the codebase, am I missing something or is that something that could be cleaned up?

indeed; i noticed that too, but didn't dig too deeply as to why it was there

> Also side note, I'm not seeing any declarations of an `.entry` section in the codebase, am I missing something or is that something that could be cleaned up? indeed; i noticed that too, but didn't dig too deeply as to why it was there
kilograham commented 2024-11-21 10:10:41 -06:00 (Migrated from github.com)

^ feel free to open separate issues/PRs

^ feel free to open separate issues/PRs
Sign in to join this conversation.
Reviewers
No reviewers
Wren6991
will-v-pi
peterharperuk
Labels
Clear labels   
bazel

   
bluetooth

   
board settings

   
boot_stage2

   
bug
Something isn't working

  
build

   
c++

   
can't reproduce
Can not reproduce the bug

  
clang

   
clib-interface

   
cmsis

   
code cleanliness

   
code size

   
compiler version issues

   
cyw43_driver

   
debug

   
discussion

   
documentation
Improvements or additions to documentation

  
duplicate
This issue or pull request already exists

  
dynamic_clock

   
elf2uf2

   
enhancement
New feature or request

  
errata

   
filesystem

   
flash layout

   
floating point

   
FreeRTOS

   
hardware_adc

   
hardware_claim

   
hardware_clocks

   
hardware_dma

   
hardware_exception

   
hardware_flash

   
hardware_gpio

   
hardware_i2c

   
hardware_irq

   
hardware_pio

   
hardware_pwm

   
hardware_rcp

   
hardware_rtc

   
hardware_spi

   
hardware_sync

   
hardware_uart

   
hardware_vreg

   
hardware_watchdog

   
hardware_xosc

   
help wanted
Extra attention is needed

  
host

   
IAR

   
installation

   
invalid
This doesn't seem right

  
linker scripts

   
lto

   
lwip

   
mbedtls

   
missing API

   
needs reporter detail

   
networking

   
newlib

   
newlib-multicore

   
non-c

   
non-cmake

   
non-gcc

   
openocd

   
orphan PR

   
OS integration

   
pico_async_context

   
pico_base

   
pico_binary_info

   
pico_flash

   
picolibc

   
pico_lwip

   
pico_malloc

   
pico_multicore

   
pico_printf

   
pico_runtime

   
pico_stdio

   
pico_stdio_usb

   
pico_sync

   
pico_time

   
pico_util

   
pioasm

   
port
issues or discussions of porting code/libraries to rp2040

  
question
Further information is requested

  
review

   
review2

   
rtos interop
Consideration for FreeRTOS co-existence

  
runtime init

   
static library

   
svd

   
test

   
tinyusb

   
vscode

   
wifi integration

   
wontfix
This will not be worked on

No labels
bazel
bluetooth
board settings
boot_stage2
bug
build
c++
can't reproduce
clang
clib-interface
cmsis
code cleanliness
code size
compiler version issues
cyw43_driver
debug
discussion
documentation
duplicate
dynamic_clock
elf2uf2
enhancement
errata
filesystem
flash layout
floating point
FreeRTOS
hardware_adc
hardware_claim
hardware_clocks
hardware_dma
hardware_exception
hardware_flash
hardware_gpio
hardware_i2c
hardware_irq
hardware_pio
hardware_pwm
hardware_rcp
hardware_rtc
hardware_spi
hardware_sync
hardware_uart
hardware_vreg
hardware_watchdog
hardware_xosc
help wanted
host
IAR
installation
invalid
linker scripts
lto
lwip
mbedtls
missing API
needs reporter detail
networking
newlib
newlib-multicore
non-c
non-cmake
non-gcc
openocd
orphan PR
OS integration
pico_async_context
pico_base
pico_binary_info
pico_flash
picolibc
pico_lwip
pico_malloc
pico_multicore
pico_printf
pico_runtime
pico_stdio
pico_stdio_usb
pico_sync
pico_time
pico_util
pioasm
port
question
review
review2
rtos interop
runtime init
static library
svd
test
tinyusb
vscode
wifi integration
wontfix
Milestone
Clear milestone
No items
No milestone
2.1.0
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
gh-raspberrypi/pico-sdk!2080
No description provided.