FreeBSD-src - Raptor Engineering's fork of pfsense FreeBSD src with pfSense changes

	Commit message (Collapse)	Author	Age	Files	Lines
*	Remove files not part of GCC 3.1.	obrien	2002-05-10	23	-3297/+0
\|
*	Use the stock [3.1-snap] version of this.	obrien	2002-02-06	3	-259/+144
\|
*	This commit was generated by cvs2svn to compensate for changes in r90075,	obrien	2002-02-01	2	-14/+80
\|\ \| \| \| \| \| \|	which included commits to RCS files with non-trunk default branches.
\| *	Enlist the FreeBSD-CURRENT users as testers of what is to become Gcc 3.1.0.	obrien	2002-02-01	5	-273/+224
\| \| \| \| \| \| \| \|	These bits are taken from the FSF anoncvs repo on 1-Feb-2002 08:20 PST.
* \|	Fix conflicts.	obrien	1999-10-16	2	-1/+17
\| \|
* \|	This commit was generated by cvs2svn to compensate for changes in r52287,	obrien	1999-10-16	5	-124/+213
\|\ \ \| \|/ \| \| \| \|	which included commits to RCS files with non-trunk default branches.
\| *	Virgin import of the GCC 2.95.1 compilers	obrien	1999-10-16	7	-125/+230
\| \|
* \|	Return these files back to their stock versions.	obrien	1999-10-13	3	-74/+142
\| \| \| \| \| \| \| \| \| \|	These files aren't used in either building GCC or with a GCC installation in the "FreeBSD native" case.
* \|	This commit was generated by cvs2svn to compensate for changes in r52143,	obrien	1999-10-12	19	-115/+1071
\|\ \ \| \|/ \| \| \| \|	which included commits to RCS files with non-trunk default branches.
\| *	Virgin import of EGCS 1.1.2	obrien	1999-10-12	22	-159/+1207
\| \|
* \|	Patches originally obtained from Bruce Evans <bde@freebsd.org> to make	peter	1996-09-18	3	-2/+32
\|/ \| \| \|	gcc "do the right thing" when running standalone on FreeBSD
*	Import of unmodified (but trimmed) gcc-2.7.2. The bigger parts of the	peter	1996-09-18	19	-0/+2962
	non-i386, non-unix, and generatable files have been trimmed, but can easily be added in later if needed. gcc-2.7.2.1 will follow shortly, it's a very small delta to this and it's handy to have both available for reference for such little cost. The freebsd-specific changes will then be committed, and once the dust has settled, the bmakefiles will be committed to use this code.