upstream/opnsense-src
1
0
Fork 0
mirror of https://github.com/opnsense/src.git synced 2026-04-09 19:37:37 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions
opnsense-src/gnu/usr.bin/cc/cc_tools/freebsd-native.h

74 lines
2.5 KiB
C
Raw Normal View History

$Id$ -> $FreeBSD$
1999-08-27 19:37:10 -04:00
/* $FreeBSD$ */
Rather than hack config/freebsd.h to contain our hacks for a native compiler, just include them in tm.h (as built from cc/cc_tools/Makefile). This will reduce the diffs from the vendor sources. Excellent idea by: jdp
1999-04-28 14:48:08 -04:00
/* FREEBSD_NATIVE is defined when gcc is integrated into the FreeBSD
source tree so it can be configured appropriately without using
the GNU configure/build mechanism. */
Define "FREEBSD_NATIVE" in the freebsd-native header to reduce the amount of stuff (and thus length of error output) we put on the invocation command line. Also follow the new FSF/GNU style of giving the symbol a value so it can be used in `if()' statements in addition to `#if' so seldomly compiled in code (on some platforms) gets compiled always, to help reduce bit-rot.
2001-03-01 21:56:59 -05:00
#define FREEBSD_NATIVE 1
Changes in order to compile GCC 3.0.2. Really irritating changes are the "forced" layering of malloc + friends in order to use the GNU versions. Sorry, we have a *very* fine malloc, and we will use it. Period. Even more irritating is that the GNU people now want to replace ctype also!! So we partially dike it out here.
2001-12-17 22:19:11 -05:00
/* Fake out gcc/config/freebsd<version>.h. */
#define FBSD_MAJOR 5
Reduce the FreeBSD custom hacks to gcc.c by using the GCC provided methods of changing the search dirs. This also removes an used search dir, removes unneeded redundancy, and a bugus dir we enherited on the i386 by baseing off of svr4.h. We went from: install: /usr/libexec/(null) programs: /usr/libexec/<OBJFORMAT>/:/usr/libexec/:/usr/bin/:/usr/libexec/ libraries: /usr/libdata/gcc/:/usr/libexec/:/usr/ccs/lib/:/usr/lib/ to: install: /usr/libexec/(null) programs: /usr/libexec/<OBJFORMAT>/:/usr/libexec/ libraries: /usr/libexec/:/usr/lib/
1999-12-22 00:00:28 -05:00
#undef SYSTEM_INCLUDE_DIR /* We don't need one for now. */
#undef TOOL_INCLUDE_DIR /* We don't need one for now. */
#undef LOCAL_INCLUDE_DIR /* We don't wish to support one. */
Rather than hack config/freebsd.h to contain our hacks for a native compiler, just include them in tm.h (as built from cc/cc_tools/Makefile). This will reduce the diffs from the vendor sources. Excellent idea by: jdp
1999-04-28 14:48:08 -04:00
Reduce the FreeBSD custom hacks to gcc.c by using the GCC provided methods of changing the search dirs. This also removes an used search dir, removes unneeded redundancy, and a bugus dir we enherited on the i386 by baseing off of svr4.h. We went from: install: /usr/libexec/(null) programs: /usr/libexec/<OBJFORMAT>/:/usr/libexec/:/usr/bin/:/usr/libexec/ libraries: /usr/libdata/gcc/:/usr/libexec/:/usr/ccs/lib/:/usr/lib/ to: install: /usr/libexec/(null) programs: /usr/libexec/<OBJFORMAT>/:/usr/libexec/ libraries: /usr/libexec/:/usr/lib/
1999-12-22 00:00:28 -05:00
/* Look for the include files in the system-defined places. */
Update for GCC 3.3.1-pre.
2003-07-11 01:33:24 -04:00
#define GPLUSPLUS_INCLUDE_DIR PREFIX"/include/c++/3.3"
#define GPLUSPLUS_BACKWARD_INCLUDE_DIR PREFIX"/include/c++/3.3/backward"
Allow the specification of a prefix for gcc to find all the various bits. If one wishes to anchor the compiler toolchain tree somewhere other than /, all one needs to do is set "TOOLS_PREFIX" to a different rooting. Submitted by: marcel (in a different format and reworked by me)
1999-12-29 09:42:46 -05:00
#define GCC_INCLUDE_DIR PREFIX"/include"
#ifdef CROSS_COMPILE
#define CROSS_INCLUDE_DIR PREFIX"/include"
Allow for better control over the GCC front-end when building a cross compiler. * Undo the diking out of cross compiler logic from gcc.c rev 1.16. * Add the `CROSS_STARTFILE_PREFIX' knob. * Add our own definition of `STANDARD_INCLUDE_DIR'. This should have been included in freebsd-native.h rev 1.5. * Minimize a little bit more, things we dike out in the FREEBSD_NATIVE case. Submitted by: ru & obrien
2002-02-20 14:41:54 -05:00
#else
#define STANDARD_INCLUDE_DIR PREFIX"/include"
Allow the specification of a prefix for gcc to find all the various bits. If one wishes to anchor the compiler toolchain tree somewhere other than /, all one needs to do is set "TOOLS_PREFIX" to a different rooting. Submitted by: marcel (in a different format and reworked by me)
1999-12-29 09:42:46 -05:00
#endif
Rather than hack config/freebsd.h to contain our hacks for a native compiler, just include them in tm.h (as built from cc/cc_tools/Makefile). This will reduce the diffs from the vendor sources. Excellent idea by: jdp
1999-04-28 14:48:08 -04:00
/* Under FreeBSD, the normal location of the compiler back ends is the
Reduce the FreeBSD custom hacks to gcc.c by using the GCC provided methods of changing the search dirs. This also removes an used search dir, removes unneeded redundancy, and a bugus dir we enherited on the i386 by baseing off of svr4.h. We went from: install: /usr/libexec/(null) programs: /usr/libexec/<OBJFORMAT>/:/usr/libexec/:/usr/bin/:/usr/libexec/ libraries: /usr/libdata/gcc/:/usr/libexec/:/usr/ccs/lib/:/usr/lib/ to: install: /usr/libexec/(null) programs: /usr/libexec/<OBJFORMAT>/:/usr/libexec/ libraries: /usr/libexec/:/usr/lib/
1999-12-22 00:00:28 -05:00
/usr/libexec directory.
``cc --print-search-dirs'' gives:
install: STANDARD_EXEC_PREFIX/(null)
Do not define a 'MD_EXEC_PREFIX'. It is not needed, not used in the cross case, and just ends up causing "/usr/libexec" being added to the library search path. Also remove misleading comment about 'STANDARD_EXEC_PREFIX'. It is needed if one does not set 'MD_EXEC_PREFIX'. Submitted by: ru
2002-02-19 22:10:54 -05:00
programs: /usr/libexec/<OBJFORMAT>/:STANDARD_EXEC_PREFIX:MD_EXEC_PREFIX
Reduce the FreeBSD custom hacks to gcc.c by using the GCC provided methods of changing the search dirs. This also removes an used search dir, removes unneeded redundancy, and a bugus dir we enherited on the i386 by baseing off of svr4.h. We went from: install: /usr/libexec/(null) programs: /usr/libexec/<OBJFORMAT>/:/usr/libexec/:/usr/bin/:/usr/libexec/ libraries: /usr/libdata/gcc/:/usr/libexec/:/usr/ccs/lib/:/usr/lib/ to: install: /usr/libexec/(null) programs: /usr/libexec/<OBJFORMAT>/:/usr/libexec/ libraries: /usr/libexec/:/usr/lib/
1999-12-22 00:00:28 -05:00
libraries: MD_EXEC_PREFIX:MD_STARTFILE_PREFIX:STANDARD_STARTFILE_PREFIX
Do not define a 'MD_EXEC_PREFIX'. It is not needed, not used in the cross case, and just ends up causing "/usr/libexec" being added to the library search path. Also remove misleading comment about 'STANDARD_EXEC_PREFIX'. It is needed if one does not set 'MD_EXEC_PREFIX'. Submitted by: ru
2002-02-19 22:10:54 -05:00
*/
Bmake bits for Gcc 3.1. Partially made possible by: Wilko.Bulte@compaq.com
2002-05-10 04:54:50 -04:00
#undef TOOLDIR_BASE_PREFIX /* Old?? This is not documented. */
MD_EXEC_PREFIX doesn't work for the cross-arch compiler. The change also makes the `cc -print-search-dirs' output sane (the pre-3.1 way) in the non-cross case. Draft reviewed by: obrien
2002-05-16 11:22:58 -04:00
#undef STANDARD_BINDIR_PREFIX /* We don't need one for now. */
Bmake bits for Gcc 3.1. Partially made possible by: Wilko.Bulte@compaq.com
2002-05-10 04:54:50 -04:00
#define STANDARD_EXEC_PREFIX PREFIX"/libexec/"
MD_EXEC_PREFIX doesn't work for the cross-arch compiler. The change also makes the `cc -print-search-dirs' output sane (the pre-3.1 way) in the non-cross case. Draft reviewed by: obrien
2002-05-16 11:22:58 -04:00
#undef MD_EXEC_PREFIX /* We don't want one. */
Read specs from /usr/libdata/gcc/specs if it exists.
2002-06-05 23:47:02 -04:00
#define FBSD_DATA_PREFIX PREFIX"/libdata/gcc/"
Rather than hack config/freebsd.h to contain our hacks for a native compiler, just include them in tm.h (as built from cc/cc_tools/Makefile). This will reduce the diffs from the vendor sources. Excellent idea by: jdp
1999-04-28 14:48:08 -04:00
/* Under FreeBSD, the normal location of the various *crt*.o files is the
/usr/lib directory. */
Allow the specification of a prefix for gcc to find all the various bits. If one wishes to anchor the compiler toolchain tree somewhere other than /, all one needs to do is set "TOOLS_PREFIX" to a different rooting. Submitted by: marcel (in a different format and reworked by me)
1999-12-29 09:42:46 -05:00
#define STANDARD_STARTFILE_PREFIX PREFIX"/lib/"
Allow for better control over the GCC front-end when building a cross compiler. * Undo the diking out of cross compiler logic from gcc.c rev 1.16. * Add the `CROSS_STARTFILE_PREFIX' knob. * Add our own definition of `STANDARD_INCLUDE_DIR'. This should have been included in freebsd-native.h rev 1.5. * Minimize a little bit more, things we dike out in the FREEBSD_NATIVE case. Submitted by: ru & obrien
2002-02-20 14:41:54 -05:00
#ifdef CROSS_COMPILE
#define CROSS_STARTFILE_PREFIX PREFIX"/lib/"
#endif
Minor reorg.
2002-04-04 14:36:33 -05:00
#undef MD_STARTFILE_PREFIX /* We don't need one for now. */
Rather than hack config/freebsd.h to contain our hacks for a native compiler, just include them in tm.h (as built from cc/cc_tools/Makefile). This will reduce the diffs from the vendor sources. Excellent idea by: jdp
1999-04-28 14:48:08 -04:00
Use libgcc_p.a when -pg is in effect. I am committing this here rather than in gcc/config/freebsd.h because the profiled libgcc only exists with the native system compiler. It is not created by a stock FSF build and we will never be able to get these bits committed to the FSF CVS repo. Thus this is very much a FreeBSD "native" issue.
2002-02-24 01:05:22 -05:00
/* For the native system compiler, we actually build libgcc in a profiled
version. So we should use it with -pg. */
When building a shared library, link it against libgcc_pic.a instead of the non-PIC libgcc.a. Linking non-pic code into a shared library is not a good thing. It happens to break amd64 at compile time, and the ppc folks want it too. The problem is mainly with C++ code, unwind-dw2.c in particular. Most of the other functions in libgcc.a are self contained so most of the time it isn't a problem. The dwarf2 unwinder is not safe though since it does make global variable references. Reviewed by: kan
2003-06-13 18:25:41 -04:00
#define LIBGCC_SPEC "%{shared: -lgcc_pic} \
%{!shared: %{!pg: -lgcc} %{pg: -lgcc_p}}"
Restore revision 1.15 (use profiled C++ libs) which wasn't on the WIP_GCC31 branch and thus was lost in the shuffle on the move to Gcc 3.1.
2002-06-08 15:58:31 -04:00
#define LIBSTDCXX_PROFILE "-lstdc++_p"
#define MATH_LIBRARY_PROFILE "-lm_p"
Allow one to profile FORTRAN77 programs.
2002-06-08 20:03:56 -04:00
#define FORTRAN_LIBRARY_PROFILE "-lg2c_p"
Use libgcc_p.a when -pg is in effect. I am committing this here rather than in gcc/config/freebsd.h because the profiled libgcc only exists with the native system compiler. It is not created by a stock FSF build and we will never be able to get these bits committed to the FSF CVS repo. Thus this is very much a FreeBSD "native" issue.
2002-02-24 01:05:22 -05:00
Rather than hack config/freebsd.h to contain our hacks for a native compiler, just include them in tm.h (as built from cc/cc_tools/Makefile). This will reduce the diffs from the vendor sources. Excellent idea by: jdp
1999-04-28 14:48:08 -04:00
/* FreeBSD is 4.4BSD derived */
#define bsd4_4
Changes in order to compile GCC 3.0.2. Really irritating changes are the "forced" layering of malloc + friends in order to use the GNU versions. Sorry, we have a *very* fine malloc, and we will use it. Period. Even more irritating is that the GNU people now want to replace ctype also!! So we partially dike it out here.
2001-12-17 22:19:11 -05:00
/* Dike out [stupid, IMHO] libiberty functions. */
#define xmalloc_set_program_name(dummy)
#define xmalloc malloc
#define xcalloc calloc
#define xrealloc realloc
#define xstrdup strdup
#define xstrerror strerror
/* And now they want to replace ctype.h.... grr... [stupid, IMHO] */
#define xxxISDIGIT isdigit
#define xxxISGRAPH isgraph
#define xxxISLOWER islower
#define xxxISSPACE isspace
#define xxxTOUPPER toupper
Reference in a new issue Copy permalink