public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "baker at usgs dot gov" <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: Wed, 19 Sep 2012 00:05:00 -0000	[thread overview]
Message-ID: <bug-54584-4-hGyAmHLdYn@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 #6 from Larry Baker <baker at usgs dot gov> 2012-09-19 00:05:38 UTC ---
Hans-Peter,

Thanks for looking at this.

This seems a bit more complicated than "just a problem with flawed elf2flt
linker placement of
orphaned sections" since elf2flt/ld.real work fine when creating flat binaries
for cases other than -msep-data/-fPIC.  That implies that they must be handling
the orphaned .tm_clone_table section for those cases (a bunch of different
-mcpu's).  I don't know where to look to find out how -msep-data/-fPIC are
handled differently, and thus, why those fail.

FYI: For the latest tests I ran, I used a vanilla binutils 1.22 distribution --
no uClinux linker patches.  I also used the latest elf2flt from
www.uclinux.org.

I also cannot find where -elf2flt is recognized/handled by collect2.  I have no
idea what collect2 does.  I tracked down the location of the error to ld.real,
which is the binutils ld, renamed to ld.real by the elf2flt package "make
install".

When I read about TM support, it sounded like it might be preferable to
pthreads.  If that is so, then I expect uClinux would be a good candidate for
TM.

I will take a look at your fix.  The details of how to write ld scripts and
such are beyond my current understanding of the process.  I learn what I have
to when I encounter a problem.  I was hoping someone that knows what to look
for would see what I have provided and instantly figure out what the problem
is. :)

Larry Baker


  parent reply	other threads:[~2012-09-19  0:05 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
2012-09-19  0:05 ` baker at usgs dot gov [this message]
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-hGyAmHLdYn@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: link
Be 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).