lang/gcc*: disable building of libssp

For today's FreeBSD 14 and earlier, libssp is a nop because nothing on
FreeBSD will be referencing these headers or lib.  On FreeBSD 15, it
actively breaks building with FORTIFY_SOURCE enabled and it's not worth
trying to make it work- the potential for GCC improvements comes from
the __builtin_object_size enhancement, not from these headers.

PR:		280265
Approved by:	salvadore (maintainer)

all: drop support for expired FreeBSD 14.0

Simplify expressions for FreeBSD 13.X

Reviewed by:	many

Differential Revision:	https://reviews.freebsd.org/D46601

lang/gcc11: Update to 11.5.0

Changes: https://gcc.gnu.org/gcc-11/changes.html#11.5

PR:		281091
Tested by:	exp-run (antoine)

lang/gcc11: enable on riscv64

Builds fine on 15-CURRENT.

PR:		272759
Approved by:	salvadore (maintainer)
MFH:		2024Q2

lang/gcc11: Moved man to share/man

Approved by:    portmgr (blanket)

lang/gcc11: remove ELFv1 support

*/*: 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/gcc11: fix build on powerpc64

Same issue as lang/gcc12 and newer.

lang/gcc11: Update to 11.4.0

Changes: https://gcc.gnu.org/gcc-11/changes.html#11.4

PR:		273397
Tested by:	exp-run (antoine)

lang/gcc11: Switch back to standard bootstrap

Switch back to STANDARD_BOOTSTRAP on i386, amd64 and aarch64 as default
option instead of LTO_BOOTSTRAP, forwarding the changes already commited
in the devel ports (commits daf12c76bd531335f58e7602afd3bc8da8fc5c33,
872d61f8ead10a6d935117876cf60057a46770ff, and
da4cb11216a7ed594d5dc453deb4693b48c3c7e9).

Users wanting to use LTO_BOOTSTRAP can still enable the option manually.

PR:		273397
Tested by:	exp-run (antoine)

lang/gcc10 lang/gcc11 lang/gcc11-devel lang/gcc12 lang/gcc12-devel lang/gcc13
lang/gcc13-devel lang/gcc14-devel: 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'

lang/gcc11: Fix build on FreeBSD 15

Update files/patch-libphobos_libdruntime_core_sys_freebsd_config.d patch
to take into account FreeBSD 15.

See also commit 929ca7ff802f14a2852122678d0c1b9e5a89be22 which already
did the same thing for lang/gcc11-devel. The new patch is indeed a copy
of the one in lang/gcc11-devel.

all: remove support for expired FreeBSD 13.1

Approved by:	portmgr (implicit), salvadore (gcc ports)
Reviewed by:	jbeich

Differential Revision: https://reviews.freebsd.org/D40845

lang/gcc*: fix build with CPUTYPE?=g[3-5]

GCC does not accept -mcpu=g4, but does accept -mcpu=G4.

lang/gcc11: Work around aarch64 extraction bug

Extraction fails with poudriere on aarch64 with the following error:

=> SHA256 Checksum OK for gcc-11.3.0.tar.xz.
tar: Pathname can't be converted from UTF-8 to current locale.
tar: Pathname can't be converted from UTF-8 to current locale.
tar: Error exit delayed from previous errors.

Enforcing use of bsdtar works around the issue. The issue is specific to
lang/gcc11 and lang/gcc12: no other GCC port is affected.

See also bug https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246670.

PR:		271052
Reported by:	Vidar Karlsen <vidar@karlsen.tech>
Reviewed by:	gerald, mikael

*: Bump PORTREVISIONs for math/mpc update to 1.3.1

*/*: Sunset 12.3-RELEASE from ports tree

- Mk/bsd.port.mk: mark FreeBSD 12.3 as unsupported.
- Mk/Uses/cabal.mk: Remove the text-2 workaround for 12.3-RELEASE
- biology/wfa2-lib: remove obsolete patch
- databases/mongodb60: remove IGNORE for EOL FreeBSD 12.3
- devel/concurrencpp: remove workaround for EOL FreeBSD 12.3
- devel/electron22: remove IGNORE for EOL FreeBSD 12.3
- devel/malloy: this should build fine on 12.4-RELEASE
- devel/qcoro: remove BROKEN for EOL FreeBSD 12.3
- devel/root: remove workaround for EOL FreeBSD 12.3
- editors/imhex: remove IGNORE for EOL FreeBSD 12.3
- emulators/ppsspp: remove workaround for EOL FreeBSD 12.3
- emulators/rpcs3: remove workaround for EOL FreeBSD 12.3
- emulators/yuzu: remove workaround for EOL 12.3-RELEASE

lang/gcc11: Mark PIE_UNSAFE

Building the port with WITH_PIE fails if STANDARD_BOOTSTRAP or
LTO_BOOTSTRAP option is enabled.

Mark PIE_UNSAFE when such an option is enabled until a better solution
is found.

PR:             268901
Reported by:    netchild

lang/gcc11: Re-execute program with ASLR disabled when necessary

Software compiled with -fsanitize=address needs ASLR to be disabled to
run successfully.

Add patches taken from the commits listed below that improve ASLR
detection and re-execute the program with ASLR disabled if necessary.

https://cgit.freebsd.org/src/commit/?id=7cafe89f9ce33effe6e471b185339d413da1ca46
https://cgit.freebsd.org/src/commit/?id=930a7c2ac67e1e8e511aa1d0a31a16c632060ebb
https://cgit.freebsd.org/src/commit/?id=96fe7c8ab0f65cf829619abd74ae6c126b21e15f

PR:		267751

lang/gcc11: Fix Address sanitizer

Software compiled with -fsanitize=address fails to run with the error
message "ASan runtime does not come first in initial library list; you
should either link runtime to your application or manually preload it
with LD_PRELOAD".

This commit fixes the issue by ignoring the [vdso] loaded shared library
instead of linux-vdso.so.

PR:		267751
Reported by:	yuri

lang/gcc11: Fix conflict on libgccjit.h and libgccjit++.h again

This is the second attempt to solve the conflict, see commits
- dc67e7d3009de2b78d96136c8ad09cf186e553df (first attempt);
- 9f0cd13014d0962aedfa016c86a5af07ca3ba814 (revert of the first
  attempt).

GCC 11, GCC 12 and GCC 13 install libgccjit.h and libgccjit++.h in the
same directory.

Fix conflict for GCC 11, which is GCC_DEFAULT, by installing those files
in a directory specific to GCC 11.

PR:		257060
Reviewed by:	yasu, jrm
Differential Revision:	https://reviews.freebsd.org/D37266

lang/gcc11: Revert "Fix conflict on libgccjit.h and libgccjit++.h"

This reverts commit dc67e7d3009de2b78d96136c8ad09cf186e553df.

The revert is necessary as

- lang/gcc11/files/patch-gcc_Makefile.in was wrong: it should have used
  $(version) instead of $(gcc_version);

- even after correcting the above mistake, the patch still does not
  work: lang/emacs fails to configure and hence to build. See also
  https://reviews.freebsd.org/D37266 .

PR:	257060
Reported by:	yasu

lang/gcc11: Fix conflict on libgccjit.h and libgccjig++.h

GCC 11, GCC 12 and GCC 13 install libgccjit.h and libgccjit++.h in the
same directory.

Fix conflict for GCC 11, which is GCC_DEFAULT, by installing those files
in a directory specific to GCC 11.

PR:		257060
Reported by:	Ting-Wei Lan <lantw44@gmail.com>
Reviewed by:	gerald, dim
Differential Revision:	https://reviews.freebsd.org/D37242
See also:	https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101491

lang/gcc11: Enable D lang compiler

Forward the part of commit f61fb49b2e76fd4f7a5b7a11510b5109206c19f2 that
enables D lang compiler.

PR:             266825
Co-authored-by: Daniel Engberg <diizzy@FreeBSD.org>

Remove WWW lines that have been moved into Makefiles

Approved by:	portmgr (implicit)

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/gcc11: Expose non-default -stdlib=libc++ support

Fix -stdlib=libc++ option which produced "error: unrecognized
command-line option '-stdlib=libc++'".

PR:		265962
Approved by:	salvadore (maintainer)
Exp-run by:	antoine (via bug 265964)

lang/gcc10,11: Take maintainership

I already maintain all other GCC supported releases ports: I adopt the
missing ones. This will allow me to deal more efficiently with changes
that affect all GCC supported releases at once.

lang: remove 'Created by' lines

A big Thank You to the original contributors of these ports:

  *  Aaron Dalton <aaron@FreeBSD.org>
  *  Adam Weinberger <adamw@FreeBSD.org>
  *  Akinori MUSHA aka knu <knu@idaemons.org>
  *  Alex Dupre <ale@FreeBSD.org>
  *  Alexey Dokuchaev <danfe@FreeBSD.org>
  *  Alonso Cardenas Marquez <acm@FreeBSD.org>
  *  Andreas Klemm <andreas@klemm.gtn.com>
  *  Andrew Pantyukhin <infofarmer@FreeBSD.org>
  *  Andrey Zakhvatov
  *  Anton Berezin <tobez@FreeBSD.org>
  *  Anton Berezin <tobez@tobez.org>

lang/gcc>=11: Warn about LTO_BOOTSTRAP

Warn users about the amount of ram and time needed to build GCC with
LTO_BOOTSTRP enabled.

PR:		264949
Reported by:	Tomoaki AOKI <junchoon@dec.sakura.ne.jp> and others
Reviewed by:	gerald
Differential Revision: https://reviews.freebsd.org/D35688

lang/gcc11: disable LTO on armv6/7

PR:	261977

lang/gcc11: upgrade to 11.3.0

This release fixes more than 189 bugs.

lang/gcc11: build with clang on powerpc64le

Copy the patch used for other gcc versions.

lang/gcc11: Add upstream patch to fix bug of libgccjit

After switching to LTO bootstrap with commit 2f6be9fb8281, build of
editors/emacs-devel fails with segmentation fault of emacs if
NATIVECOMP option is enabled. The cause of the problem is bug of
libgccjit and it was unveiled by switching to LTO bootstrap. So add
upstream patch to fix it.

PR:		263271
Approved by:	gerald (toolchain@)

lang/gcc11: switch gcc11 to LTO bootstrap

lang/gcc11-devel with LTO builds fine on the cluster, switch lang/gcc11 as well.

lang/gcc11: Relinquish maintainership

After working on (and largely maintaining) our GCC ports for some
20 years, time has come to hand over the baton.

Sadly despite multiple requests nobody stepped up (even having waited
several months after relinquishing maintainership other gcc* ports),
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

lang/gcc11: Update to GCC 11.2

This minor release fixes more than 95 bugs.

lang/gcc11: New port cloned from gcc11-devel

Welcome GCC 11.1, the first release of the GCC 11 series!

https://gcc.gnu.org/gcc-11/changes.html has a comprehensive overview
of many improvements and changes and
https://gcc.gnu.org/gcc-11/porting_to.html highlights issues you may
encounter porting to this version. This release series should not
prove too disruptive, mainly C++ defaulting to GNU++17 and some more
libstdc++ headers will need to be included explicitly.

To give a brief overview of some of the more noticable changes:

Some short options of the gcov tool have been renamed: -i to -j and
-j to -H.