Compiling Objective-C code for the Epiphany

[GreggChandler]

[CocoaGeek]

[CocoaGeek]

... and here's the linker map output.

[GreggChandler]

Thanks for the update. The "-Wl,--defsym=..." commands are only necessary if you want to build code for multiple cores--so you could try leaving them out for now. Legacy.ldf appears to default to the first core if they are not specified. However, you appear to have them correct so that probably is not really an issue. I am just trying to simplify the argument list.

The next step appears to be tracking down the assertion failure. I am wondering if the partitioned address space is still too small. I did not edit or revise any of the calculations. I did change the stack. It would also be worth tracking down -Os. I don't know which specific optimizations it executes. If it generates short calls, and the program is too big, that might be a problem. However, I don't know which specific optimizations it uses. Again, just an uninformed guess.

I forgot that --specs=nosys.specs was in my Makefile. It may not be necessary in your case. I don't use malloc() and friends, but I suspect Objective C will. But again, that should not affect linking, only execution.

According to Google, the error does occur on other architectures. At times it appears related to PIC, which you aren't specifying. Other times PIC appears to be the fix. I hope that I have not taken you too far afield. I need to reproduce the error somehow. I'll try and look up the assertion. I was hoping 796 was a line number within the source file--but not according to source I can currently find.

[CocoaGeek]

Same error when my library is compiled with -fPIC than without.

[GreggChandler]

Here is another interesting link regarding this message:

Have you tried a simple hello world type application?

[CocoaGeek]

You are correct, I have an external library which .o files I include in my library and I had forgotten to remove -fPIC from their compilation. Now it's linking without error ... however, the code isn't running on the core. If I use e-run on the device with the Epiphany executable I get an "illegal instruction at 0x108, program stopped with signal 4 (Illegal instruction)" error. Haven's tried to debug that yet.

Update #1: I have to use --e-external-fetch with e-run to get it to run (the illegal instruction was caused by that)
Update #2: A simple C based test runs just fine (even with your legacy.ldf), but linking my lib cause it to not run

[GreggChandler]

It sounds like you are making progress. I wouldn't have expected any code at 0x108. I didn't try running with e-run. I could possibly try putting the stack back in external memory with legacy.ldf?

If it links but doesn't run, I would start to look at how malloc() and friends work. The specs stuff can impact this. I don't know what the "new lib" does here, as I do my own memory allocation. Obviously heap is important. I believe legacy puts the heap in external memory. Perhaps I broke that?

[GreggChandler]

[GreggChandler]

Isn't e-run the simulator? Have you tried e-loader?