From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Joern Rennecke <joern.rennecke@embecosm.com>
Cc: GDB Patches <gdb-patches@sourceware.org>,
Pedro Alves <palves@redhat.com>
Subject: Re: [PATCH] Create avr-linux-tdep.c (add reintroduce gdbarch_gdb_signal_{to,from}_target for that target)
Date: Mon, 12 Aug 2013 21:49:00 -0000 [thread overview]
Message-ID: <m3siyevauu.fsf@redhat.com> (raw)
In-Reply-To: <20130812171901.7mi3vkyoro40kwcc-nzlynne@webmail.spamcop.net> (Joern Rennecke's message of "Mon, 12 Aug 2013 17:19:01 -0400")
On Monday, August 12 2013, Joern Rennecke wrote:
> Quoting Sergio Durigan Junior <sergiodj@redhat.com>:
>
>
>> +avr-*-*linux*)
>> + # Target: AVR Linux
>> + gdb_target_obs="avr-tdep.o avr-linux-tdep.o linux-tdep.o"
>> + gdb_sim=../sim/avr/libsim.a
>> + ;;
>> +
>> avr-*-*)
>> # Target: AVR
>> gdb_target_obs="avr-tdep.o"
>>
>
> That is creating a new target.
Yes.
> So are users using a linux host supposed
> to configure for this new target? But why does it look like it's the
> target that is running linux - there is no such thing for avr.
> Shouldn't we rather autoconf the host signals?
These are not host signals, they are the target's.
Maybe I am confusing things here. I saw
<arch/avr32/include/uapi/asm/signal.h> and I assumed one could run Linux
on AVR, but on a further investigation I saw that it only applies to
AVR32, right? I'm definitely not an expert here, sorry about it.
But well, if that is the case, then I guess we can either (a) treat
AVR32 separately and make an avr32-linux-tdep.c for it, or (b) drop this
patch entirely.
WDYT? Am I missing something here?
--
Sergio
next prev parent reply other threads:[~2013-08-12 21:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 19:47 Sergio Durigan Junior
2013-08-12 21:19 ` Joern Rennecke
2013-08-12 21:49 ` Sergio Durigan Junior [this message]
2013-08-13 14:16 ` Pedro Alves
2013-08-13 16:00 ` Sergio Durigan Junior
2013-08-25 4:51 ` Mike Frysinger
2013-08-25 19:42 ` Sergio Durigan Junior
2013-08-26 3:41 ` Mike Frysinger
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=m3siyevauu.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=joern.rennecke@embecosm.com \
--cc=palves@redhat.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