microblaze: apply gdb patches from meta-xilinx repository #11
Conversation
alpsayin
force-pushed
the
zephyr-gdb-12.1-microblaze-recipes-27082023
branch
from
f5e57a5 to
b594ebe
Compare
alpsayin
changed the title
alpsayin
force-pushed
the
zephyr-gdb-12.1-microblaze-recipes-27082023
branch
from
b594ebe to
18d1778
Compare
alpsayin
force-pushed
the
zephyr-gdb-12.1-microblaze-recipes-27082023
branch
from
18d1778 to
c8e8e46
Compare
|
@stephanosio resolved the marked issues and some more that I noticed irrelevant to microblaze. Something bad happens during startup though. I'm inspecting this one further. |
alpsayin
force-pushed
the
zephyr-gdb-12.1-microblaze-recipes-27082023
branch
2 times, most recently
from
d0b3a0f to
8fed488
Compare
This patchset fixes many known issues on gnu-toolchain for microblaze. But mainly the atomic-cas and binutils incorrect relocation issues. For gdb this patchset resolves the segfault caused by inline-sniffer. Patches obtained from https://github.com/xilinx/meta-xilinx/ repository, from meta-microblaze/recipes-devtools/gdb/gdb path. I've filtered out microblaze64 and microblaze-linux patches because they cause microblaze-gdb to segfault at startup and more importantly, unnecessary for Zephyr. Below is a list of patches applied and squashed: 0008-Patch-MicroBlaze.patch Signed-off-by: Alp Sayin <alpsayin@gmail.com>
alpsayin
force-pushed
the
zephyr-gdb-12.1-microblaze-recipes-27082023
branch
from
8fed488 to
ffe6d2f
Compare
|
@stephanosio It's the damn microblaze64 or linux-microblaze ports again. I've filtered them out and kept one important patch that resolves a really annoying issue. Ready for re-review. Considering that only a single patch is left I'm half-expecting that I'll be asked to apply the original commit with its author,date and message but with a bit of Zephyr commit guideline application |
Given that the original patch is fairly void of any useful information, the current commit looks good. |
microblaze: apply gdb patches from meta-xilinx repository
This patchset fixes many known issues on gnu-toolchain for microblaze.
But mainly the atomic-cas and binutils incorrect relocation issues.
Patches obtained from https://github.com/xilinx/meta-xilinx/ repository,
from meta-microblaze/recipes-devtools/gdb path.
Introduction of Microblaze64 didn't break gdb build, so Ive decided to let it be.