NetBSD/gnu
phx 1872c0f94c Applied a patch from Roman Zippel to fix jump table addressing in the M68k
codegen.

Taken from the gcc mailing list January 2007:
http://gcc.gnu.org/ml/gcc-patches/2007-01/msg02476.html

2007-01-30  Roman Zippel <zippel@linux-m68k.org>

        * config/m68k/m68k.c (output_move_himode)
	config/m68k/m68k.md: remove jump table recognition
	* config/m68k/m68k.c (ASM_OUTPUT_CASE_FETCH): use simple pc
	relative addressing

Approved by Christos Zoulas, Alistair Crooks and Matthew Green.
2008-11-20 22:53:17 +00:00
..
dist Applied a patch from Roman Zippel to fix jump table addressing in the M68k 2008-11-20 22:53:17 +00:00
lib add ${LDOPTS} to the compile command. 2008-10-26 07:04:04 +00:00
usr.bin pass HOST_CFLAGS when building cross tools 2008-11-04 23:58:40 +00:00
usr.sbin Use ${TOOL_AWK} instead of ${AWK} or plain "awk" in make commands. 2008-10-19 22:05:19 +00:00
Makefile goodbye uucp 2006-11-12 01:20:00 +00:00
README netbsd.org -> NetBSD.org 2003-12-04 23:32:37 +00:00

$NetBSD: README,v 1.5 2003/12/04 23:32:37 keihan Exp $

Organization of Sources:

This directory hierarchy is using a new organization that
separates the GNU sources from the BSD-style infrastructure
used to build the GNU sources.  The GNU sources are kept in
the standard GNU source tree layout under:

	dist/*

The build infrastructure uses the normal BSD way under:

	lib/*
	usr.bin/*

The makefiles in the above hierarchy will "reach over" into
the GNU sources (src/gnu/dist) for everything they need.


Maintenance Strategy:

The sources under src/gnu/dist are generally a combination of
some published distribution plus changes that we submit to the
maintainers and that are not yet published by them.  There are
a few files that are never expected to be submitted to the FSF,
(i.e. BSD-style makefiles and such) and those generally should
stay in src/gnu/lib or src/gnu/usr.bin (the BSD build areas).

Make sure all changes made to the GNU sources are submitted to
the appropriate maintainer, but only after coordinating with the
NetBSD maintainers by sending your proposed submission to the
<tech-toolchain@NetBSD.org> mailing list.  Only send the changes
to the third-party maintainers after consensus has been reached.