Fix uninitialised CRIS insn

[Alan Modra]

On Mon, Jun 16, 2014 at 07:11:54AM +0200, Hans-Peter Nilsson wrote:
> > From: Alan Modra <amodra@gmail.com>
> > Sender: "binutils-owner@sourceware.org" <binutils-owner@sourceware.org>
> 
> > Fixes "FAIL: gas/cris/rd-bkw4v32" with MALLOC_PERTURB_=1
> > 
> > gas/
> > 	* config/tc-cris.c (md_create_long_jump): Follow "short" jump
> > 	with a nop rather than leaving uninitialised.
> > gas/testsuite/
> > 	* gas/cris/rd-bkw4v32.d: Update.
> 
> Thanks, though there are more.  For cris-elf, cris-linux and
> mmix-knuth-mmixware, your changes has caused spurious extra
> error messages.  (Please don't adjust the expected error
> messsages to match; the bug is that the extra lines are
> emitted.)

Yes, I know.  I mentioned that in a later message.  The extra errors
are a result of calling write_object_file() after as_bad() occurred,
something that only happened before with the -Z option.

I was hoping you'd deal with the testcase errors, rather than have
me blundering around in your ports.

-- 
Alan Modra
Australia Development Lab, IBM