From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: gdb-patches@sources.redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Resurrect sh64 target
Date: Wed, 30 Mar 2005 18:09:00 -0000 [thread overview]
Message-ID: <200503301809.j2UI94ea020905@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20050330174336.GQ2495@cygbert.vinschen.de> (message from Corinna Vinschen on Wed, 30 Mar 2005 19:43:36 +0200)
Date: Wed, 30 Mar 2005 19:43:36 +0200
From: Corinna Vinschen <vinschen@redhat.com>
Hi,
the below patch resurrects sh64-elf. I reworked the sh64 code so that it
doesn't use any deprecated mechanism anymore but all new stuff, except for
the DEPRECATED_TM_FILE, which I'm not sure how to circumvent.
By investing some time in truly multi-arching the shared library code.
Andrew has made it absolutely clear (by reverting one of my patches)
that you're not allowed to check something in that sets
DEPRECATED_TM_FILE. I'm still a bit frustrated at that, so sorry for
this unhelpful message.
Mark
next prev parent reply other threads:[~2005-03-30 18:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-30 17:44 Corinna Vinschen
2005-03-30 18:09 ` Mark Kettenis [this message]
2005-03-31 7:51 ` Corinna Vinschen
2005-04-13 15:20 ` Corinna Vinschen
2005-04-13 18:23 ` Mark Kettenis
2005-04-15 8:01 ` Corinna Vinschen
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=200503301809.j2UI94ea020905@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sources.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