GCC, the GNU Compiler Collection, supports a number of languages.
This port installs the C, C++, and Fortran front ends as gcc9, g++9,
and gfortran9, respectively.
Gerald Pfeifer <gerald@FreeBSD.org>
===> The following configuration options are available for gcc9-9.5.0_2:
BOOTSTRAP=on: Build using a full bootstrap
MULTILIB=on: Build support for 32-bit and 64-bit targets
===> Use 'make config' to modify these settings
*/*: Sunset 12.4-RELEASE/12-STABLE from ports tree
- Remove all references to defunct ARCH arm
- Remove all references to defunct ARCH sparc64
- Remove x11-drivers/xf86-video-sunffb which requires defunct sparc64
ARCH
- Remove sysutils/afbinit requires defunct sparc64 ARCH
- Remove all references to bktr driver
- Remove all references to defunct FreeBSD_12
- Remove all references to OSVERSION/OSREL corresponding to 12
- Remove conditionals in Mk/Uses/cabal.mk
- Remove sparc reference from Mk/Uses/qt-dist.mk
- Remove BROKEN_sparc64/NOT_FOR_ARCH=sparc64
- Remove BROKEN_FreeBSD_12* from:
- Remove OpenSSL patches from:
- Remove conditional flags for OSVERSION >= 1300000 to fixed flags.
Also move conditional flags for non sparc64/arm ARCH to fixed flags.
Reviewed by: brooks, jbeich, rene, salvadore
Differential Revision: https://reviews.freebsd.org/D42068
lang/gcc8 lang/gcc9: fix build with libc++ 17
When building relatively recent gcc ports (with C++ in them) against
libc++ 17, you get errors similar to:
In file included from
/wrkdirs/usr/ports/lang/gcc12/work/gcc-12.2.0/gcc/cp/module.cc:208:
In file included from
/wrkdirs/usr/ports/lang/gcc12/work/gcc-12.2.0/gcc/system.h:239:
In file included from /usr/include/c++/v1/vector:321:
In file included from /usr/include/c++/v1/__format/formatter_bool.h:20:
In file included from /usr/include/c++/v1/__format/formatter_integral.h:32:
In file included from /usr/include/c++/v1/locale:202:
/usr/include/c++/v1/__locale:546:5: error: '__abi_tag__' attribute only
applies to structs, variables, functions, and namespaces
546 | _LIBCPP_INLINE_VISIBILITY
| ^
/usr/include/c++/v1/__config:813:37: note: expanded from macro
'_LIBCPP_INLINE_VISIBILITY'
(Only the first 15 lines of the commit message are shown above )
Move more WWW entries from pkg-descr files into Makefiles
The WWW: lines in the pkg-descr files of these ports where not at the
end of those files and have been missed in prior conversion runs.
Approved by: portmgr (implicit)
lang/gcc9: deprecate
gcc9 is now EOL'd and shouldn't be used anymore.
Since this is the last release that builds on powerpc64 elfv1 (with GCC 4.2),
set the expiration date to FreeBSD 12.x EOL date.
lang/gcc9: Relinquish maintainership
After working on (and largely maintaining) our GCC ports for more than
19 years, time has come to hand over the baton.
Sadly despite multiple requests nobody stepped up (even having waited
another 3+ months after relinquishing maintainership of gcc9-devel),
so pass maintainership to toolchain@.
Fix CONFLICTS entries of multiple ports
There have been lots of missing CONFLICTS_INSTALL entries, either
because conflicting ports were added without updating existing ports,
due to name changes of generated packages, due to mis-understanding
the format and semantics of the conflicts entries, or just due to
typoes in package names.
This patch is the result of a comparison of all files contained in
the official packages with each other. This comparison was based on
packages built with default options and may therefore have missed
further conflicts with optionally installed files.
Where possible, version numbers in conflicts entries have been
generalized, some times taking advantage of the fact that a port
(Only the first 15 lines of the commit message are shown above )
lang/gcc9: Update to the GCC 9.4 release
This fixes more than 190 bugs compared to GCC 9.3.
files/patch-gcc_dumpfile.c has made it upstream in the meantime, so
remove it on our end.
Update to MPC version 1.2.0 with the following changes:
- New functions:
. mpc_sum
. mpc_dot
- Several functions are more robust with a reduced exponent range
(for example corresponding to IEEE 754 binary formats).
- New mpcheck tool for comparison with the native C library (which
is not installed by default).
Bump all directly dependent ports. Do not bump those indirectly
dependent via the lang/gcc* family since their run-time dependencies
and code generated should not be affected.
PR: 249950
Submitted by: wen
Back port part of r566296 | gerald | 2021-02-22 from lang/gcc9-devel:
[B]ack port of part of r565301 | gerald | 2021-02-15 from
lang/gcc11-devel:
Explicitly build --without-zstd such that archivers/zstd isn't pulled
in inadvertedly when present in the build system even though it is not
an explicit dependency. [1]
Back port part of r566885 | gerald | 2021-03-01 from lang/gcc9-devel:
Remove the GRAPHITE option. Graphite still is a largely experimental
feature, so better left to newer versions of GCC such as GCC 10 which
is now our default.
PR: 253286 [1]
Back port part of r554445 | gerald | 2020-11-08 from lang/gcc9-devel:
Also remove SSP_UNSAFE which was added by r327697 in 2013 to the
pre-pre-...-predecessor of this port and does not appear necessary
any longer.
Back port part of r555542 | gerald | 2020-11-17 from lang/gcc9-devel:
Fold the PLUGINS option, which has been on by default, into standard
behavior and remove that option. It has not been causing any issues
since we enabled it 11 months ago, nor measurable overhead.
PR: 242644
Improve upon revision 532950 by passing GCC optimization options via
MAKE_ARGS instead of trying to do this via the environment (which is
lower priority and required files/patch-Makefile.in which we can now
remove).
PR: 245511
lang/gcc9: build with base GCC on powerpc64 elfv1
Instead of using lang/gcc8 for bootstrapping gcc9 on powerpc64 elfv1, use
directly base gcc.
Necessary changes:
- CFLAGS_FOR_TARGET="-O0" CXXFLAGS_FOR_TARGET="-O0" BOOT_CFLAGS="-O0" in
CONFIGURE_ENV and MAKE_ENV. Otherwise bootstrapped compiler fails later in the
build with segfault.
- CRTSTUFF_T_CFLAGS has changed optimizations to -O0, instead of -O2. -O2 worked
in gcc8, because there was no -fno-asynchronous-unwind-tables flag added to
CRTSTUFF_T_CFLAGS. Since this works when building with clang on powerpc64 elfv2,
this patch is added to EXTRA_PATCHES, only on powerpc64 elfv1,
- BOOT_CFLAGS has added ? before =. This is to allow overriding BOOT_CFLAGS in
CONFIGURE_ENV and MAKE_ENV.
- A patch by Gustavo Romero to gcc/dumpfile.c is necessary to allow compiling
with base GCC, otherwise base GCC hits ICE. Incidentally, this patch alone also
fixes build for powerpc (32 bits) with base GCC.
Bump PORTREVISION for dependency change.
PR: 245511, 242506
Approved by: gerald (maintainer timeout)
Update to the GCC 9.3 release, which fixes some 157 further bugs.
This remains the default version of GCC in the Ports Collection, and
this update mostly addresses regressions.
files/patch-powerpc32 was a backport from this release branch to begin
with and has now become obsolete. [1]
PR: 241125 [1]
Temporarily apply a patch from upstream that addresses a build failure
on powerpc ("error: integer constant is too large for 'long' type").
This is already part of lang/gcc9-devel after r518494 and the 20191123
snapshot of GCC 9.2.1; it will be part of the GCC 9.3 release at which
point we can remove this local patch again.
PR: 241125
Forward port r517702 | gerald | 2019-11-15 from lang/gcc9-devel:
On versions of FreeBSD that that are new enough and made that switch
already, use ELFv2 ABI on powerpc64.
PR: 239813
Submitted by: pkubaj
Reported by: linimon
Backport 517206 | gerald | 2019-11-10 from lang/gcc10-devel, which already
landed in lang/gcc9-devel as r517355 | gerald | 2019-11-13.
Add a new option PLUGINS that enables GCC's plugin framework. This is off
by default for now, but something to possibly make the default after a bit
of settling.
I plan to backport this to lang/gcc9-devel and then lang/gcc9.
Submitted by: David Carlier <devnexen@gmail.com>
Differential Revision: https://reviews.freebsd.org/D22292
clang on rs6000/powerpc* unfortunately poisons user namespace by default
(without any special options or include files being required).
Until that changes (or GCC changes) we need to avoid using vec_step as a
variable name.
PR: 239266
Update to GCC 9.2 release, the second in the GCC 9 series, which fixes
some 68 bugs.
This is the default version of GCC in the Ports Collection, and it just
got a bit more polish and stability.
Both files/patch-amd64-gcc-multilib-support and
files/patch-powerpc64-no-_GNU_SOURCE [1] have been integrated upstream
(and also been part of lang/gcc9-devel already), so remove them here.
PR: 239648 [1]
Ensure _GNU_SOURCE is now longer defined on powerpc64 (which was a
regression from the GCC 8 series).
The technical background is that a consolidation in upstream GCC made
non-GNU platforms include gnu-user.h and then undefined some macros
in rs6000/freebsd.h, but missed doing the same in rs6000/freebsd64.h.
The has now been included upstream and the current snapshot that the
lang/gcc9-devel port tracks; carrying files/patch-powerpc64-no-_GNU_SOURCE
in this port should become obsolete with the GCC 9.2 release.
(As this should be a very short-lived measure, bump PORTREVISION only
for powerpc64 to avoid all other users having to rebuild, too.)
PR: 239648
Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
Welcome GCC 9.1, the first release of the GCC 9 series!
https://gcc.gnu.org/gcc-9/changes.html has a comprehensive overview of
many improvements and changes and https://gcc.gnu.org/gcc-8/porting_to.html
addresses issues you may encounter porting to this new version, though
this release series should have fewer of those than previous ones.
To provide a brief overview of some of the more noticable changes:
GCC's diagnostics now print source code with a left margin showing line
numbers. This is configurable via -fno-diagnostics-show-line-numbers.
Plus there have been lots of further improvements around diagnostic
messages in general as -fopt-info.
As usual a large number of improvements to code generation, including
(Only the first 15 lines of the commit message are shown above )