Conflicts:

	modules/wishbone/wishbone_pkg.vhd

Conflicts:

	modules/wishbone/Manifest.py

common/gc_crc_gen: fixed reverse_range bug causing invalid CRCs, added restart input and combinatorial output to reduce latency

Conflicts:

	modules/common/gc_crc_gen.vhd

Conflicts:

	modules/common/gc_crc_gen.vhd

Conflicts:

	modules/genrams/xilinx/Manifest.py

Conflicts:

	modules/genrams/xilinx/Manifest.py
	modules/genrams/xilinx/generic_dpram_sameclock.vhd
	modules/genrams/xilinx/spartan6/generic_sync_fifo.vhd

Conflicts:

	modules/common/Manifest.py
	modules/common/gencores_pkg.vhd

The LM32 needs a read-enable.
Unfortunately, Xilinx does not have one, so we emulate it.

By using altsyncram directly, we get the follow benefits:
  * clear control of read-write resolution behaviour
  * can specify a mif file for initialization
  * eliminates warnings about dual-port clock inference timings

On Altera, "" generates a null-range warning.
When the dpram is used heavily, these warnings add up to many.

The RW ordering on address conflict varies by platform.
Some platforms only support some options.
Most of the dprams in WR are portable and don't depend on the order.
This new option allows a core to specify that it does not care what
the result of a RW conflict is, and thus work on more platforms.

For Xilinx, "dont_care" = "read_first", the old default.

On both Altera and Xilinx, a dual port memory can achieve twice the
bit-width per memory block when there is a single reader and writer.
This adds a place-holder generic_simple_dpram for Xilinx so that code
using the purpose-built variant for Altera continues to work on ISE.

In the past we used a generic to set the initial memory contents on altera.
Unfortunately, quartus compiles big generics slowly (read: hours).
Now we can load from a .mif file instead, which is much faster (seconds).
Thus, this old option is no longer needed.

There were many constructs like this:
  gen_with_empty : if(g_with_empty) generate
    empty_o <= empty;
  end generate gen_with_empty;

If g_with_empty is true, then there are no warnings.
If g_with_empty is false, then empty_o is unset and empty is unused.

There is no improvement in performance/resource utilization to explicitly
cutting these signals. The optimizer will happily discard unused logic.

The alternative of adding
  gen_without_empty : if(not g_with_empty) generate
    empty_o <= 'X';
  end generate gen_without_empty;
will remove the empty_o unset warning, but not the empty unused warning.

This patch does make it possible for designs to  use empty_o without
setting g_with_empty; an error. On the other hand, those designs had
undefined behaviour before anyway, so they might have worked unreliably.

CFG_EBA_RESET is supposed to be the default value of the LM32's eba_reset
parameter. Unfortunately, the constant leaked into the sources directly.

In order to clean-up a truncation warning for pc_f, it was easiest to fix
the missing parameter and then use a subarray of that value.