public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/54584] m68k-uclinux error: Link tests are not allowed after GCC_NO_EXECUTABLES Date: Tue, 18 Sep 2012 23:30:00 -0000 [thread overview] Message-ID: <bug-54584-4-98vQ2pfQTd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54584-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54584 --- Comment #5 from Hans-Peter Nilsson <hp at gcc dot gnu.org> 2012-09-18 23:30:23 UTC --- This seems to be just a problem with flawed elf2flt linker placement of orphaned sections. But, I can't find where -elf2flt is handled in FSF binutils; you need to talk to whomever is in charge of the local uclinux linker patches. For a linker fix, either add a "${RELOCATING+*(.tm_clone_table)}" in the .text or .data output section of the default linker script or improve the elf2flt orphaned section placement, similar to what I did in <http://sourceware.org/ml/binutils/2012-09/msg00101.html> as a partial fix for PR54373. (It fixes the main problem, but I found others.) Generic ELF already has good enough orphaned-section placement that no real ELF target has any problem with .tm_clone_table actually being an orphaned section for all targets. Of course, an alternative is to cover up by disabling transactional memory, likely the most pragmatic solution; I'm guessing TM is of little interest to uclinux targets. :)
next prev parent reply other threads:[~2012-09-18 23:30 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-14 20:44 [Bug target/54584] New: " baker at usgs dot gov 2012-09-15 0:39 ` [Bug target/54584] " baker at usgs dot gov 2012-09-18 2:45 ` baker at usgs dot gov 2012-09-18 21:43 ` baker at usgs dot gov 2012-09-18 21:53 ` baker at usgs dot gov 2012-09-18 23:30 ` hp at gcc dot gnu.org [this message] 2012-09-19 0:05 ` baker at usgs dot gov 2012-09-19 0:15 ` baker at usgs dot gov
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-54584-4-98vQ2pfQTd@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).