From: Doug Evans <dje@transmeta.com>
To: Doug Evans <dje@transmeta.com>
Cc: DJ Delorie <dj@delorie.com>,
binutils@sources.redhat.com, cgen@sources.redhat.com,
sid@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: New Sanyo Stormy16 relocations
Date: Tue, 17 Dec 2002 12:14:00 -0000 [thread overview]
Message-ID: <15871.34195.719221.180542@casey.transmeta.com> (raw)
In-Reply-To: <15871.33865.254007.550012@casey.transmeta.com>
Doug Evans writes:
> > > But, if approval is required, methinks binutils is a better place to
> > > provide approval for .opc changes (e.g. complaints about warnings :-).
> >
> > Better than sid? Better than gdb?
>
> I don't understand. The context here is .opc. files.
> Changes to .opc files don't affect sid or gdb. Only binutils.
[flipping the pedantic bit]
Ok, gdb uses the disassembler.
Still, if src/opcodes is ok for binutils, I don't think
it's a problem for gdb or sid.
And if it is, the problem can be dealt with as it arises.
next prev parent reply other threads:[~2002-12-17 20:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1039041358.28757.307.camel@p4>
[not found] ` <20021204225643.GS27956@bubble.sa.bigpond.net.au>
[not found] ` <1039043233.28767.313.camel@p4>
[not found] ` <200212170353.gBH3r9f14238@envy.delorie.com>
[not found] ` <15871.31192.305439.813418@casey.transmeta.com>
2002-12-17 11:47 ` DJ Delorie
2002-12-17 11:56 ` Frank Ch. Eigler
2002-12-17 12:09 ` Doug Evans
2002-12-17 12:14 ` Doug Evans [this message]
2002-12-18 2:37 ` Andrew Cagney
2002-12-18 7:47 ` Frank Ch. Eigler
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=15871.34195.719221.180542@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=binutils@sources.redhat.com \
--cc=cgen@sources.redhat.com \
--cc=dj@delorie.com \
--cc=gdb@sources.redhat.com \
--cc=sid@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).