public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Bart Veer <bartv@cygnus.co.uk>
To: advanc@dial.eunet.ch
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] ecosSWtools problems
Date: Wed, 11 Aug 1999 05:58:00 -0000	[thread overview]
Message-ID: <199908111258.NAA19916@sheesh.cygnus.co.uk> (raw)
In-Reply-To: <37B05076.C11E7B92@dial.eunet.ch>

>>>>> "Robin" == Robin Farine <advanc@dial.eunet.ch> writes:

    Robin> Hi, This posting does not concern ecos directly but it may
    Robin> help some ecos users, so ...

    Robin> 1. When linking code with PC REL24 branches, the ARM bfd
    Robin> linker does not complain nor modify the branch instruction
    Robin> when the offset overflows, it just generates code that
    Robin> branch anywhere. The attached patch should fix this
    Robin> problem.

I passed this on to the gcc team, and the patch has been incorporated
into the master binutils sources (with a few minor changes). I have
also listed the problem and the patch on the known problems list,
http://sourceware.cygnus.com/problemlist.html . Thanks!

    Robin> 2. The '--gc-sections' linker flag causes the linker to
    Robin> discard referenced code. For instance:

    <snip>

    Robin>    Now, my questions:
    Robin>     - did I miss something?
    Robin>     - if not then I think that gcc is the culprit since
    Robin>       '.vtable_inherit' does not have anything to do with virtual
    Robin>       inheritance, right?

This one has also been passed on to the gcc team for comments. 

Bart Veer // eCos net maintainer

      parent reply	other threads:[~1999-08-11  5:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-10  9:20 Robin Farine
1999-08-11  0:13 ` [ECOS] ecosSWtools problems.2 Robin Farine
1999-08-11  5:58 ` Bart Veer [this message]

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=199908111258.NAA19916@sheesh.cygnus.co.uk \
    --to=bartv@cygnus.co.uk \
    --cc=advanc@dial.eunet.ch \
    --cc=ecos-discuss@sourceware.cygnus.com \
    /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).