From: Mike Frysinger <vapier@gentoo.org>
To: crossgcc@sourceware.org
Cc: Michael Hope <michael.hope@linaro.org>,
"Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>,
Zhenqiang Chen <zhenqiang.chen@linaro.org>
Subject: Re: [PATCH] debug/gdb: --disable-sim for CT_GDB_CROSS
Date: Wed, 23 Nov 2011 18:34:00 -0000 [thread overview]
Message-ID: <201111231334.15434.vapier@gentoo.org> (raw)
In-Reply-To: <CANLjY-=MPbhNmQQO=srou9fGzdgOciT7EQAr=tXMWQgZS=Rm3A@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1117 bytes --]
On Tuesday 22 November 2011 20:48:15 Michael Hope wrote:
> On Wed, Nov 23, 2011 at 6:21 AM, Yann E. MORIN wrote:
> > Otherwise, I agree with Mike: Why is it needed to disable 'sim' in the
> > cross-gdb? If the build is broken for some archs, it should rather be
> > fixed. At least, disabling/enabling 'sim' should be a config option,
> > so users that want to try and/or fix it have an easy way to.
>
> I'd like to disable sim as it isn't useful when building for a GLIBC
> target and it's one more thing to support. ARM don't want to
> distribute a binary simulator due to IP reasons which I must admit
> I've never understood :)
that's not generally true. it depends on the target whether the sim supports
Linux syscalls, dynamic libraries, etc...
the Blackfin sim certainly supports not only newlib/bare metal code (which also
includes Linux/bootloaders), but also uClibc/FDPIC/FLAT Linux user programs.
i've seen other sims in there that support Linux userland targets.
sounds like it should be made into a config option for people to control if
*they* don't want the sim.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-11-23 18:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 11:20 Zhenqiang Chen
2011-11-22 15:29 ` Mike Frysinger
2011-11-22 17:21 ` Yann E. MORIN
2011-11-23 1:48 ` Michael Hope
2011-11-23 2:41 ` Khem Raj
2011-11-23 3:44 ` Zhenqiang Chen
2011-11-23 18:34 ` Mike Frysinger [this message]
2012-01-29 21:15 ` Yann E. MORIN
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=201111231334.15434.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=crossgcc@sourceware.org \
--cc=michael.hope@linaro.org \
--cc=yann.morin.1998@anciens.enib.fr \
--cc=zhenqiang.chen@linaro.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).