public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: David Fernandez <david.fernandez.work@googlemail.com>
To: John Dallaway <john@dallaway.org.uk>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Re: eCos arm-eabi GNU tools - test release 4.6.3-20120623
Date: Tue, 26 Jun 2012 21:50:00 -0000	[thread overview]
Message-ID: <4FEA2EA8.7020703@googlemail.com> (raw)
In-Reply-To: <4FE9982C.9020605@dallaway.org.uk>

Hi John,

On 26/06/12 12:08, John Dallaway wrote:
> I have generated a new test release of the GNU tools for ARM targets.
> The new test release avoids an issue with the length of GDB 'g' packet
> replies when working with Cortex-M targets that was seen with the
> previous test release. GDB is now built from 7.4.1 sources with an
> M-profile patch based on current GDB sources.
Could you provide a link to the patch tarball? I usually build the
tool-chain, and like to try that.
>  GCC 4.6.3 is now built
> with additional multilib setup for Cortex-A9 processors.
Now that you mention multilib, I noticed that, when building gcc for
arm-eabi, cpus like cortex-m3 require you (perhaps that is my mistake)
to build it --with-cpu=cortex-m3 --with-mode=thumb (at least), so that
newlib's crt0.S gets compiled in thumb-2 mode, so that the right code is
generated when using the options -mcpu=cortex-m3 -mthumb.

I wonder why crt0.S is not compiled multiple times with all the options
required for the cpus and modes supported by the arm-eabi target... I
thought that multilib was to ensure that (although I may be wrong about
that).

Do you know something about this? The crossgcc list seems to be very
quiet, and nobody there seems to be willing to give an answer on that.

Cheers
David Fernandez

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  parent reply	other threads:[~2012-06-26 21:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-26 11:08 [ECOS] " John Dallaway
2012-06-26 11:44 ` [ECOS] Fwd: " Ilija Kocho
2012-07-27 11:37   ` Alex Schuilenburg
2012-07-30  9:38     ` Ilija Kocho
2012-07-30 10:09       ` Sergei Gavrikov
2012-07-31 11:48         ` Alex Schuilenburg
2012-06-26 21:50 ` David Fernandez [this message]
2012-06-27  7:00   ` [ECOS] " John Dallaway
2012-06-27 11:29     ` David Fernandez
2012-06-27 12:09       ` Ilija Kocho
2012-06-27 16:22         ` David Fernandez
2012-06-27 16:38           ` Stanislav Meduna
2012-06-27 16:49             ` Ilija Kocho
2012-06-28 20:05               ` David Fernandez
2012-06-28 20:01             ` David Fernandez
2014-06-13 10:25 ` [ECOS] eCos arm-eabi GNU tools - " John Dallaway

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=4FEA2EA8.7020703@googlemail.com \
    --to=david.fernandez.work@googlemail.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=john@dallaway.org.uk \
    /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).