From: Maxim Kuvyrkov <maxim@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: [PATCHES, M68K] Various fixes and improvements for M68K and ColdFire
Date: Tue, 17 Nov 2009 12:15:00 -0000 [thread overview]
Message-ID: <4B029388.5070001@codesourcery.com> (raw)
Hi,
I'm submitting the following series of patches on behalf of my
colleagues at CodeSourcery. These patches fix a couple of issues in
m68k support and generally improve support for ColdFire subarchitecture.
The cumulative patch was test on coldfire-elf and coldfire-linux targets
with no regressions. ColdFire-elf results show several progressions
while coldfire-linux results show many progressions.
--
Maxim Kuvyrkov
CodeSourcery
maxim@codesourcery.com
(650) 331-3385 x724
next reply other threads:[~2009-11-17 12:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 12:15 Maxim Kuvyrkov [this message]
2009-11-17 12:22 ` [PATCH, M68K] Handle lack of FPU registers Maxim Kuvyrkov
2009-11-17 12:28 ` [PATCH, M68K] Add regformat file for ColdFire registers Maxim Kuvyrkov
2009-11-17 12:34 ` [PATCH, M68K] Fix initialization Maxim Kuvyrkov
2009-11-17 12:36 ` [PATCH, M68K] Support xml testsuite Maxim Kuvyrkov
2009-11-17 15:40 ` [PATCHES, M68K] Various fixes and improvements for M68K and ColdFire Daniel Jacobowitz
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=4B029388.5070001@codesourcery.com \
--to=maxim@codesourcery.com \
--cc=gdb-patches@sourceware.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