[Bug 245511] lang/gcc9: build with base GCC on powerpc64 elfv1

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245511

Gerald Pfeifer <gerald at FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|Open                        |In Progress

--- Comment #6 from Gerald Pfeifer <gerald at FreeBSD.org> ---
(In reply to Piotr Kubaj from comment #5)
> Thanks, it indeed works. I thought I tested that approach already, but
> I clearly didn't.

Excellent.  I'll apply my change to lang/gcc9 in a minute then.

> Please, don't disable gcc9-devel for powerpc*. Even if there are no users
> of those on powerpc*, gcc*-devel serve as great testing bed to check that
> the next release will build just fine (especially because you don't do
> tests on powerpc*). This is why I think that gcc10-devel should build as
> well, even though no port depends on it (regarding to my earlier PR about
> gcc10-devel on powerpc64 elfv2).

I understand, yet if that is an important function of the -devel ports
for powerpc as well (I certainly see it that way in general), can you
help test lang/gcc9-devel and push in changes there first before tackling
lang/gcc9 going forward?

I will port my change to lang/gcc9-devel and see that the dumpfile.c build
fix get backported from upstream head to the GCC 9 release branch, so that
lang/gcc9-devel will get it via the following weekly snapshot.

> Why are those changes crippling GCC? I understand that it will run slower, 
> but so is the case already for GCC 7 and 8. I think it's still better from
> relaying on bootstrap compiler.

Your change does not just affect the compiler binaries themselves, and I
assume quite a bit, it also pushes -O0 for the target libraries.

The GCC documentation has the following:

  @code{BOOT_CFLAGS} does not apply to bootstrapped target libraries.
  Since these are always compiled with the compiler currently being
  bootstrapped, you can use @code{CFLAGS_FOR_TARGET} to modify their
  compilation flags, as for non-bootstrapped target libraries.

Once my patch is in, can you please give three things a try, one after
the other?

 (1) CXXFLAGS_FOR_TARGET is really necessary (by removing it)?
 (2) CFLAGS_FOR_TARGET is really necessary (by removing it)?
 (3) For what is left after (1) and (2), is -O1 also sufficient?

If you run into a problem for the above, can you please share the last
lines of the build log, in particular the invocation that fails and where
in the chain of make invocations this is (usually the last few lines of the
log)?

-- 
You are receiving this mail because:
You are on the CC list for the bug.