Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: Yao Qi <yao@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Remove board setting `gdb,cannot_call_functions'
Date: Tue, 01 May 2012 02:34:00 -0000	[thread overview]
Message-ID: <20120501023412.GA21734@host2.jankratochvil.net> (raw)
In-Reply-To: <4F96B0D7.4040506@redhat.com>

On Tue, 24 Apr 2012 15:55:35 +0200, Pedro Alves wrote:
> The powerpc-sim ones could still be relevant, and tested, I suppose.

I have disabled powerpc-sim build in 2008 as it cannot run even a hello world
testcase. There was some small change in 2008, maybe some changes last in
2006, I doubt powerpc-sim can be used anymore.


Thanks,
Jan


      parent reply	other threads:[~2012-05-01  2:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-23 13:18 Yao Qi
2012-04-23 13:42 ` Tom Tromey
2012-04-24 14:13 ` Pedro Alves
2012-04-24 14:36   ` Yao Qi
2012-05-01  2:34   ` Jan Kratochvil [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=20120501023412.GA21734@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=yao@codesourcery.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