PATCH: verilog hex memory dump backend for BFD

[Anthony Green]

On Mon, 2009-04-27 at 15:29 +0100, Nick Clifton wrote:
> Hi Anthony,
> 
> > Ping.  Thanks!
> 
> Sorry - I was looking at this over the weekend.
> 
> >> 2009-04-22  Anthony Green  <green@moxielogic.com>
> >>
> >>         * verilog.c: New file.
> >>         * Makefile.am (BFD32_LIBS): Add verilog.c.
> >>         (BFD32_LIBS_CFILES): Add verilog.c.
> >>         (verilog.lo): New build rule.
> >>         * Makefile.in: Rebuilt.
> >>         * targets.c: Add verilog support.
> >>         * bfd-in2.h: Add verilog support.
> 
> Approved and applied.  I made two small changes - the patch to bfd-in2.h 
> really needed to be applied to bfd.h, and a quick mention of the new 
> support was needed in binutils/NEWS.
> 

In the NEWS file, you refer to it as the "verilog binary file format".
There is something called the verilog binary file format, but this isn't
it.   This is the verilog memory hex dump format.  The "binary files"
serve the same purpose as the hex files, but instead of ASCII hex digits
it's a text file full of '1' and '0' strings.  I've committed this minor
but obvious tweak to the NEWS file...


2009-04-29  Anthony Green  <green@moxielogic.com>

	* NEWS: Tweak verilog support description.

Index: binutils/NEWS
===================================================================
RCS file: /cvs/src/src/binutils/NEWS,v
retrieving revision 1.80
diff -u -r1.80 NEWS
--- binutils/NEWS	27 Apr 2009 14:27:36 -0000	1.80
+++ binutils/NEWS	30 Apr 2009 03:56:11 -0000
@@ -1,7 +1,7 @@
 -*- text -*-
 
-* The verilog binary file format is now supported as an output format
for
-  objcopy.
+* The verilog memory hex dump file format is now supported as an output
format
+  for objcopy.
 



> Cheers
>    Nick
> 
>