06:00 gerald 

Update to the 20180510 snapshot of GCC 8.3.1.

 

07:13 gerald 

Update to the 20180503 snapshot of GCC 8.3.1.

On the way forward port r499061 | gerald | 2019-04-15 from lang/gcc8 [1]:

  GCC has two runtime libraries:  The static library libgcc.a (-lgcc) and
  the shared library libgcc_s.so (-lgcc_s).  Both implement many of the
  same functions but they also each have their unique functions.  When
  GCC links programs and libraries there are three possibilities:

  1. gcc -static-libgcc or gcc -static: -lgcc
     => Just use libgcc.a.

  2. gcc -shared-libgcc: -lgcc_s -lgcc
     => Link with libgcc_s first, so libgcc.a is only used for its unique
        functions.

  3. gcc: -lgcc -Wl,--as-needed -lgcc_s -Wl,--no-as-needed
     => Link with libgcc.a first so libgcc_s is only used for its unique
        functions (_Unwind_* functions).

  Approach 3 is the default for gcc and it's also what clang and clang++ use;
  approach 2 is the default for gfortran, g++ and probably other front ends.

  This patch makes 3 the default for gfortran.  It significantly reduces
  the use of libgcc_s.  The _Unwind_* functions are also available in the
  old base system libgcc_s which means this reduces the need for
  -rpath /usr/local/lib/gccN in ports that depend on libraries built with
  gfortran.  Consider a dependency tree like this:

    prog -> libA -> libgcc_s (old base system libgcc_s is fine)
         -> libB -> libgcc_s (libB built with gfortran, needs new libgcc_s)

  Here prog needs to be linked with -rpath /usr/local/lib/gccN even if it's
  a normal C program compiled with clang.  Without -rpath it will fail to
  start because it loads old libgcc_s first as a dependency of libA and then
  it fails to load libB.  With this patch libB works with old base system
  libgcc_s or may not need libgcc_s at all, so prog does not need to be
  linked with -rpath.

PR:		208120 [1]
Submitted by:	tijl [1]

 

05:13 gerald 

Update to the 20180426 snapshot of GCC 8.3.1.

 

15:49 gerald 

Update to the 20180419 snapshot of GCC 8.3.1.

 

14:11 gerald 

Update to the 20180412 snapshot of GCC 8.3.1.

 

05:00 gerald 

Update to the 20180405 snapshot of GCC 8.3.1.

 

16:10 gerald 

Update to the 20180329 snapshot of GCC 8.3.1.

 

11:24 gerald 

Update to the 20180322 snapshot of GCC 8.3.1.

 

11:41 gerald 

Update to the 20180315 snapshot of GCC 8.3.1.

 

15:20 gerald 

Update to the 20180308 snapshot of GCC 8.3.1.

No longer require a not too old version of GCC to build on powerpc64, but
rely on the system compiler (even if that means we need to be explicitly
conservative when it comes to optimizations). [1]

Sync pkg-descr with lang/gcc7-devel, in particular after r442530 there.

PR:		235975 [1]
Submitted by:	Piotr Kubaj <pkubaj@anongoth.pl> [1]

 

03:01 gerald 

Update to the 20180301 snapshot of GCC 8.3.1.

Simplify the creation of the multilib-related sub-directory tree on
powerpc64 and avoid leaving an empty directory behind on the way. [1]

Sync pkg-descr with lang/gcc7-devel, in particular after r442530 there.

PR:		235964, 231804 [1]
Discussed with:	Piotr Kubaj <pkubaj@anongoth.pl> [1]

 

09:46 gerald 

Update to the 20180222 snapshot of GCC 8.3.1, the first after the release
of GCC 8.3 (hence the increased version number).

 

06:17 gerald 

Update to the 20180215 snapshot of GCC 8.2.1.

 

06:50 gerald 

Update to the 20180208 snapshot of GCC 8.2.1.

 

07:04 gerald 

On powerpcspe configure GCC --with-cpu=8548 instead of --with-cpu=8540,
which caused the build to fail after the update to binutils 2.31 and was
factually incorrect anyways (the oldest we support being 8548). [1]

On the way update to the 20180201 snapshot of GCC 8.2.1.

PR:		235393 [1]
Reported by:	jhibbits [1]
Tested by:	jhibbits [1]

 

09:03 gerald 

Update to the 20180125 snapshot of GCC 8.2.1.

 

16:53 gerald 

Update to the 20180118 snapshot of GCC 8.2.1.

Forward port r490785 | gerald | 2019-01-20 from lang/gcc8: [1]

  Update files/patch-spe-config (and with that our local adjustments to
  config.gcc) to the changed directory structure under gcc/config brought
  by GCC 8 when powerpcspe was cloned and broken out from the regular
  powerpc port.

PR:		234419 [1]
Submitted by:	jhibbits [1]
MFH:		2019Q1 (build fix on powerpcspe) [1]

 

01:08 gerald 

Update to the 20180111 snapshot of GCC 8.2.1.

 

19:26 gerald 

Update to the 20180104 snapshot of GCC 8.2.1.

Forward port r469788 from lang/gcc6 = backport r475105 from lang/gcc8:

  Filter the -mretpoline command-line option, which is understood by
  recent versions of clang (and used in the context of the Spectre
  security issues), but not GCC (which uses different options for the
  same) from CFLAGS and CXXFLAGS.

  This avoids the build of this port via bootstrap, which is the default
  and leverages both the system compiler (clang in most cases) plus a just
  built version GCC, to fail due to the latter not knowing -mretpoline.

PR:		228205
Submitted by:	rozhuk.im@gmail.com

 

21:45 gerald 

Update to the 20181228 snapshot of GCC 8.2.1.

 

02:28 gerald 

Update to the 20181221 snapshot of GCC 8.2.1.

 

16:56 gerald 

Update to the 20181214 snapshot of GCC 8.2.1.

 

15:53 gerald 

Update to the 20181207 snapshot of GCC 8.2.1.

 

10:52 gerald 

Update to the 20181130 snapshot of GCC 8.2.1.

 

04:17 gerald 

Update to the 20181123 snapshot of GCC 8.2.1.

Move items belonging into the USES block earlier in the Makefile,
and into a separate block. [1]

Reported by:	portlint [1]

 

04:25 gerald 

Update to the 20181116 snapshot of GCC 8.2.1.

 

14:34 gerald 

Update to the 20181109 snapshot of GCC 8.2.1.

 

16:42 gerald 

Update to the 20181102 snapshot of GCC 8.2.1.

Remove an empty line to have a conditional dependency of dejagnu for
the testsuite directly in the dependency block.

 

20:29 gerald 

Update to the 20181026 snapshot of GCC 8.2.1.

 

11:00 gerald 

Update to the 20181019 snapshot of GCC 8.2.1.

 

06:26 gerald 

Update to the 20181012 snapshot of GCC 8.2.1.

 

18:00 gerald 

Update to the 20181005 snapshot of GCC 8.2.1.

This brings a partial fix for what was reported in PR 231804 that I made
upstream, cf. https://gcc.gnu.org/ml/gcc-patches/2018-10/msg00076.html .

PR:		231804

 

22:12 gerald 

Update to the 20180928 snapshot of GCC 8.2.1.

 

08:09 gerald 

Update to the 20180921 snapshot of GCC 8.2.1.

 

00:36 gerald 

Update to the 20180914 snapshot of GCC 8.2.1.

 

09:34 gerald 

Update to the 20180907 snapshot of GCC 8.2.1.

 

12:18 gerald 

Update to the 20180831 snapshot of GCC 8.2.1.

 

11:59 gerald 

Update to the 20180824 snapshot of GCC 8.2.1.

 

00:11 gerald 

Update to the 20180817 snapshot of GCC 8.2.1.

 

13:35 gerald 

Update to the 20180810 snapshot of GCC 8.2.1.

 

13:56 gerald 

Update to the 20180803 snapshot of GCC 8.1.1.

 

08:55 gerald 

Now that GCC 8.2 is out, update to the 20180727 snapshot of GCC 8.2.1
in preparation of the cycle leading up to the GCC 8.3 release in a few
months.

Functionally this is pretty much equivalent to the 8.2 release for the
time being.

 

17:50 gerald 

Update to the 20180713 snapshot of GCC 8.1.1.

 

16:07 gerald 

Update to the 20180706 snapshot of GCC 8.1.1.

 

19:25 gerald 

Update to the 20180629 snapshot of GCC 8.1.1.

 

22:16 gerald 

Update to the 20180622 snapshot of GCC 8.1.1.

 

07:51 gerald 

Update to the 20180615 snapshot of GCC 8.1.1.

 

01:49 gerald 

Update to the 20180608 snapshot of GCC 8.1.1.

 

14:09 gerald 

Update to the 20180601 snapshot of GCC 8.1.1.

 

12:12 gerald 

Update to the 20180525 snapshot of GCC 8.1.1.

 

18:10 gerald 

Update to the 20180518 snapshot of GCC 8.1.1.

 

12:23 gerald 

Update to the 20180511 snapshot of GCC 8.1.1.

 

19:35 gerald 

Update to the 20180504 snapshot of GCC 8.1.1.  This is just after the
release of GCC 8.1 (the first of the GCC 8 series) and thus pretty much
the same, hence the jump in version number from 8.0.1 to 8.1.1.

Add a conflict with the soon forthcoming lang/gcc8 port that is going
to track GCC 8 releases.

 

10:36 gerald 

Update to the 20180422 snapshot of GCC 8 which is getting really close
to the release of GCC 8 (aka GCC 8.1).

 

13:19 gerald 

Update to the 20180415 snapshot of GCC 8.

 

16:40 gerald 

Update to the 20180408 snapshot of GCC 8.

 

12:31 gerald 

Update to the 20180401 snapshot of GCC 8.

 

06:30 gerald 

Update to the 20180325 snapshot of GCC 8.

 

23:53 gerald 

Update to the 20180318 snapshot of GCC 8.

 

09:04 gerald 

Update to the 20180311 snapshot of GCC 8.

 

08:47 gerald 

Update to the 20180308 snapshot of GCC 8.

 

20:48 gerald 

Update to the 20180225 snapshot of GCC 8.

 

01:19 gerald 

Update to the 20180211 snapshot of GCC 8.

 

21:59 gerald 

Update to the 20180204 snapshot of GCC 8.

 

16:12 gerald 

Update to the 20180128 snapshot of GCC 8.

 

09:16 gerald 

Update to the 20180121 snapshot of GCC 8, which now carries a version
number of 8.0.1 instead of 8.0.0 due to the late stage in the release
process.

 

08:27 gerald 

Update to the 20180114 snapshot of GCC 8.

 

04:09 gerald 

Update to the 20180107 snapshot of GCC 8.

 

22:53 gerald 

Update to the 20171231 snapshot of GCC 8.

 

05:03 gerald 

Update to the 20171224 snapshot of GCC 8 (after the snapshot the week
before failed to build).

 

11:28 gerald 

Update to the 20171210 snapshot of GCC 8.

The issue that triggered my workaround in files/patch-gcc_tree-cfg.c
has been addressed upstream based on my report, so this local patch
can be removed.  (It would conflict anyway.)

 

12:37 gerald 

Update to the 20171203 snapshot of GCC 8.

I pushed files/patch-clang3.4.1-fixes upstream, so remove it here.

 

18:51 gerald 

Update to the 20171126 snapshot of GCC 8.

This requires two temporary patches to allow for building with
clang 3.4.1 (on FreeBSD 10.4) and trimming down an overeager check
that breaks Wine, for example.

Forward port revision 454177 from lang/gcc7: [1]

Make sure what we install is stripped (i.e., debug info is removed).

The straightforward way is setting INSTALL_TARGET to install-strip,
which is supported by the upstream GCC build machinery.

Unfortunately this fails when running as regular user (non-root)
since strip requires write permission to the files in question,
and we install binaries as r-xr-xr-x by default.  To work around
that we need to set BINMODE to allow for write access by the user,
something that's common on GNU/Linux (which is why this probably
has not been noticed there).  This is not necessary when running
as root.

(A different approach suggested was to set STRIP=true, alas that
leads to many files actually not being stripped.  This is due to
GCC using its own script install-sh that in turn uses cp, chmod,
strip,...  instead of our own install-* tools in many cases.)

Reported by:	Ports QA Framework, miwi, sobomax [1]
Discussed with:	tijl, miwi [1]
Differential Revision:	https://reviews.freebsd.org/D10357 [1]

 

23:39 gerald 

Update to the 20171119 snapshot of GCC 8.

Remove the setting of CXXFLAGS / STAGE1_CXXFLAGS to -fbracket-depth=512
for armv6 which should not be required here (and is not for armv7 and
aarch64 according to tests done by andreast@).

Use .elif instead of distinct .if sequences for architecture-specific
settings, something I plan on rolling out throughout all lang/gcc* ports.

 

13:54 gerald 

Update to the 20171112 snapshot of GCC 8.

 

21:53 gerald 

Update to the 20171105 snapshot of GCC 8.  This addresses a real-world
issue around threading and unwinding that andreast@ has fixed upstream
(cf. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82635 ).

 

10:52 gerald 

Update to the 20171029 snapshot of GCC 8.  This should fix potential
build failures on some newer versions of FreeBSD.

 

18:40 gerald 

Update to the 20171022 snapshot of GCC 8.

 

15:51 gerald 

Update to the 20171008 snapshot of GCC 8.

Enable this on armv7 as well, courtesy of andreast@ pushing support
upstream. [1]

PR:		221905 [1]

 

11:55 gerald 

Update to the 20171008 snapshot of GCC 8.

 

21:20 gerald 

Update to the 20171001 snapshot of GCC 8.

 

21:51 gerald 

Update to the 20170924 snapshot of GCC 8.

 

20:24 gerald 

Update to the 20170917 snapshot of GCC 8.

On the way remove quotes around constant strings compared with ${ARCH}. [1]

PR:		221905 [1]
Submitted by:	linimon [1]

 

14:55 gerald 

Update to the 20170910 snapshot of GCC 8 skipping last week's snapshot
which failed to build for us.

 

11:08 gerald 

Update to the 20170827 snapshot of GCC 8.

 

21:39 gerald 

Update to the 20170820 snapshot of GCC 8.

Move ONLY_FOR_ARCHS according to portlint.

 

12:40 gerald 

Update to the 20170813 snapshot of GCC 8.

 

18:23 gerald 

Update to the 20170806 snapshot of GCC 8.

 

11:26 gerald 

Update to the 20170730 snapshot of GCC 8.

 

11:53 gerald 

Update to the 20170723 snapshot of GCC 8.

Remove workaround for PR 219274 that bapt@ had put in place in 2014
from pkg-plist. [1]

PR:		219274 [1]

 

21:30 gerald 

Update to the 20170716 snapshot of GCC 8.

 

07:48 gerald 

Update to the 20170709 snapshot of GCC 8.

 

01:02 gerald 

Update to the 20170702 snapshot of GCC 8.

Remove headers being created by GCC's fixincludes machinery from the
installation / packaging to avoid breakage when FreeBSD's headers are
changing afterwards.  Several fellow committers have strongly indicated
that our headers do not need the kind of adjustments that GCC performs.

 

15:27 gerald 

Update to the 20170625 snapshot of GCC 8.

 

21:30 gerald 

Update to the 20170611 snapshot of GCC 8.

 

05:25 gerald 

Update to the 20170604 snapshot of GCC 8.

Adjust WWW reference in pkg-descr to https and avoid a trailing slash.

 

00:21 gerald 

Update to the 20170528 snapshot of GCC 8.  Upstream now ships sources
as .tar.xz over .tar.bzip2 for the last few years, so adjust USES.

 

20:28 gerald 

Update to the 20170521 snapshot of GCC 8.

 

13:08 gerald 

Update to the 20170507 snapshot of GCC 8.

 

09:46 gerald 

Update to the 20170430 snapshot of GCC 8.