From: Simon Marchi <simark@simark.ca>
To: Kevin Buettner <kevinb@redhat.com>, gdb-patches@sourceware.org
Cc: Mike Frysinger <vapier@gentoo.org>
Subject: Re: [PATCH] FT32: support for FT32B processor - part 1
Date: Mon, 09 Oct 2017 14:38:00 -0000 [thread overview]
Message-ID: <2f16fed2-0b14-5a50-93fa-38593a254985@simark.ca> (raw)
In-Reply-To: <20171007100121.4173f763@pinnacle.lan>
On 2017-10-07 01:01 PM, Kevin Buettner wrote:
> On Wed, 4 Oct 2017 16:51:02 +0000
> James Bowman <james.bowman@ftdichip.com> wrote:
>
>> FT32B is a new FT32 family member. It has a code
>> compression scheme, which requires the use of linker
>> relaxations. The change is quite large, so submission
>> is in several parts.
>>
>> Part 1 adds a 15-bit instruction field, and CPU-specific functions for
>> the code compression that are used in binutils and GDB.
>>
>> This patch contains the gdb changes. The corresponding binutils patch is
>> https://sourceware.org/ml/binutils/2017-10/msg00010.html
>>
>> OK to commit?
>
> Hi James,
>
> I've looked over your patch. While I have not researched the specifics
> of the FT32B, your patch looks reasonable to me.
>
> I would approve this patch if I could, but after looking at
> sim/MAINTAINERS it seems that only Mike Frysinger may approve this
> patch.
>
> Kevin
>
There is no maintainer listed for ft32 architecture, both in gdb/ and sim/.
Maybe it would be useful to have some, so arch-specific changes can go through
them (just throwing the idea out there).
Simon
prev parent reply other threads:[~2017-10-09 14:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 16:51 James Bowman
2017-10-07 17:01 ` Kevin Buettner
2017-10-09 14:38 ` Simon Marchi [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=2f16fed2-0b14-5a50-93fa-38593a254985@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=vapier@gentoo.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