NetBSD/gnu
uwe 86fd3cca3a Fix gcc codegen bug that manifests during generation of stack
protector code for sh3.  Details in gcc pr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32163

Author: kkojima
Date: Sun Jun  3 04:38:52 2007
New Revision: 125292

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=125292
Log:
        PR target/32163
        * config/sh/sh.md (symGOT_load): Don't schedule insns when
        the symbol is generated with the stack protector.


Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/config/sh/sh.md
2007-06-03 21:02:44 +00:00
..
dist Fix gcc codegen bug that manifests during generation of stack 2007-06-03 21:02:44 +00:00
lib Regen: remove sh5 support from sh3 tools. 2007-04-20 11:13:23 +00:00
usr.bin Add new Makefile knob, USE_FORT, which extends USE_SSP by turning on the 2007-05-28 12:06:17 +00:00
usr.sbin Add new Makefile knob, USE_FORT, which extends USE_SSP by turning on the 2007-05-28 12:06:17 +00:00
Makefile goodbye uucp 2006-11-12 01:20:00 +00:00
README

$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.