Experimental Support for Microblaze 64-bit Architecture - binutils and gdb

[Gopi Kumar Bulusu]

> > As  gas/ld/rob (rest of binutils) are producers of elf and gdb is a
> consumer adding experimental microblaze 64-bit support patches  in the
> former (bfd)  and not latter will mean gdb built from the exact same
> binutils-gdb code base won't be able to process the mb64 binaries and any
> one planning to run/debug the binaries with gdb will not be able to do so.
> Also the reason for starting with binutils-gdb before contributing
> > patches to gcc.
>
> If you first add support for 64-bit to gas/ld (and even gcc), I presume
> that debugging 32-bit Microblaze programs with gdb will keep working.
> Debugging 64-bit Microblaze programs with gdb will not work (yet), but
> that is not a regression.
>
Anyhow, given that binutils and gdb are in the same repo, it would be
> fine to send changes to binutils and gdb in the same patch series (but
> in properly separated patches).  binutils maintainer will approve
> binutils patches, and gdb maintainers will approve gdb patches.
>

Thanks, will try to follow the most efficient path.


> > Also, as part of this effort I had to merge bintutils binutils-gdb and
> > gdb binutils-gdb patches for the target from Xilinx git that have over
> > the years digressed. I think It will be a good idea to keep them in
> > sync as part of this effort.
>
>
> Having everything upstream is the best way to avoid diverging and
> staying stuck with an old version.
>

Yes, microblaze-32 / microblaze-64 are expected to take this path.


> Thanks a lot for working on this.
>

Many thanks for your response.

gopi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://sourceware.org/pipermail/binutils/attachments/20240717/7f484586/attachment.htm>