-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
internal error, aborting at /binutils/bfd/amigaoslink.c line 569 in get_relocated_section_contents #13
Comments
Removing am_mapamiga.s from the code and just replacing it with the c function in am_map.c didn't help and just shifted the problem somewhere else. Be aware, DoomAttack is not compiled with -fbaserel (much of it is implemented in assembly and all of them use absolute symbol references) |
well, the binutils linker wants all code sections named |
Confirmed. I moved all assembly files' section directives to .text and it passed the linking stage. But I could swear it already linked before that. On a sidenote, would it be possible to allow sections with non-gcc names? It would relieve some of the linker pressure to stuff everything together in -msmall-code and -fbaserel modes. The programmer had more control over which code/data needs to go together and which code can be in separate sections (via long jumps). Obviously I didn't think this through yet, but sounds desirable. |
I just reactivated the amiga hunk format. The aout format only supports 2 real sections, one .text and one .data section. Even the .bss is in fact only an extension to .data. With amiga hunk format an unlimited count of sections should work with one limitation: Only one baserel .data section is allowed. |
Is there anything you ask me to test? |
I am trying to create a minimal problem... |
Ha, it's not a binutil issue, it's section naming issue: the instruction is:
pc relative jumps between different sections are impossible. |
https://github.com/mheyer32/DoomAttack
When linking this project, one of the recent changes to binutils is now causing the issue below.
I wanted to file against the binutils project, but there seems to be no way to report issues(?)
The text was updated successfully, but these errors were encountered: