From: Andrew Cagney <ac131313@cygnus.com>
To: Johan Rydberg <johan.rydberg@netinsight.se>
Cc: binutils@sources.redhat.com,
GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: Re: [PATCH] OpenRISC support for opcodes
Date: Mon, 30 Apr 2001 18:37:00 -0000 [thread overview]
Message-ID: <3AEE134F.813BC06C@cygnus.com> (raw)
In-Reply-To: <3AE5AC52.5B3BA916@netinsight.se>
Johan Rydberg wrote:
> * openrisc-asm.c: New file.
> * openrisc-desc.c: Likewise.
> * openrisc-desc.h: Likewise.
> * openrisc-dis.c: Likewise.
> * openrisc-ibld.c: Likewise.
> * openrisc-opc.c: Likewise.
> * openrisc-opc.h: Likewise.
FYI, these file names clash on an 8.3 system.
While GDB only insists on files used by native DJGPP/MINGW builds being
8.3 compliant, it does still ask people adding non- 8.3 compliant files
to ensure that those files are renamed to something 8.3 compliant using
the table:
src/gdb/config/djgpp/fnchange.lst
If you're wondering, opcodes updates are instantly included in a GDB
distro.
enjoy,
Andrew
next parent reply other threads:[~2001-04-30 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3AE5AC52.5B3BA916@netinsight.se>
2001-04-30 18:37 ` Andrew Cagney [this message]
2001-05-03 3:36 ` Eli Zaretskii
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=3AEE134F.813BC06C@cygnus.com \
--to=ac131313@cygnus.com \
--cc=binutils@sources.redhat.com \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=johan.rydberg@netinsight.se \
/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