problem with bfin-linux-fdpic

Sam James sam@gentoo.org
Mon Mar 17 14:51:39 GMT 2025


Waldemar Brodkorb <wbx@openadk.org> writes:

> Hi Sam,
> Sam James wrote,
>
>> 
>> 
>> > On 17 Mar 2025, at 10:15, Waldemar Brodkorb <wbx@openadk.org> wrote:
>> > 
>> > Hi Sam,
>> > Sam James wrote,
>> 
>> Hi!
>> > 
>> >> Waldemar Brodkorb <wbx@openadk.org> writes:
>> >> 
>> >>> Hi,
>> >>> 
>> >>> I have an Arcturus Blackfin board I am using for experimenting with
>> >>> uClibc-ng. It is a bf548 CPU.
>> >>> Binutils 2.26 with this patch¹ works fine.
>> >>> Binutils 2.27 does not work anymore.
>> >>> 
>> >>> A simple hello world gives me an "Illegal Instruction".
>> >>> 
>> >>> I tried to git bisect the problem, but I only get some unrelated
>> >>> gdb commit as the culprit of the problem.
>> >>> 
>> >> 
>> >> You can pass --disable-gdb when bisecting to not build the other stuff
>> >> in the repository (see
>> >> https://github.com/thesamesam/sam-gentoo-scripts/blob/main/gcc/bisect-binutils
>> >> for a full list of options you can disable for bisecting just binutils).
>> > 
>> > Thanks, but I already use --disable-gdb.
>> > See
>> > https://cgit.openadk.org/cgi/cgit/openadk.git/tree/toolchain/binutils/Makefile#n56
>> > 
>> 
>> Show me the error you got? May need to disable gdbserver too (possibly other bits as well).
>
> I don't get a compile error. The toolchain generation works fine. The problem exist when I am running the
> generated code. Do you want to see a stacktrace from the target?

Sorry, I'd clearly misread it - thinking you meant "bisection failed
because it hit GDB compile errors", my fault.

Does `git bisect log` show some reasonable good+bad pattern, or was it
all-good or all-bad? I'd definitely make sure the tools as expected were
used (note that if using w/ GCC, you'll need to do
-B/path/to/binutils-pfx for wherever you're bisecting with).

I can't help with bfin specifics as I've only ever played with it once, though.

thanks,
sam


More information about the Binutils mailing list