[Bug target/80865] broken compilation on Mac OS X 10.5 / powerpc: unrecognizable insn

2017-09-05 Thread pkg at 1tein dot de 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80865

Christian Cornelssen  changed:

   What|Removed |Added

 CC||pkg at 1tein dot de

--- Comment #2 from Christian Cornelssen  ---
Bug confirmed on a ppc64 (G5) darwin9 platform with the GCC 7.2.0 release as
used in the MacPorts gcc7/libgcc port
(https://github.com/macports/macports-ports/tree/master/lang/gcc7), commit
ff4c4bd
(https://github.com/macports/macports-ports/commit/ff4c4bd6219f166b85c82c44eecb909dd3ae08b3).

Same error, same location.

Also confirmed that the patches referred to in Comment 1 let the build succeed.
Attaching them in a cumulated form suitable for `patch -p0`.

[Bug target/80865] broken compilation on Mac OS X 10.5 / powerpc: unrecognizable insn

2017-09-05 Thread pkg at 1tein dot de 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80865

--- Comment #3 from Christian Cornelssen  ---
Created attachment 42124
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42124&action=edit
Darwin/PPC patches mentioned in
https://gcc.gnu.org/ml/gcc-testresults/2017-01/msg02971.html

[Bug target/80865] broken compilation on Mac OS X 10.5 / powerpc: unrecognizable insn

2017-09-20 Thread pkg at 1tein dot de 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80865

--- Comment #5 from Christian Cornelssen  ---
Related MacPorts gcc7 ticket:

https://trac.macports.org/ticket/54215

That thread contains confirmations that the build succeeds with the patches of
comment 1 (cumulated in attachment 42124) and test results for powerpc-darwin9
(MacOS X Leopard) plus x86_64-darwin16 (MacOS Sierra).

[Bug target/80865] broken compilation on Mac OS X 10.5 / powerpc: unrecognizable insn

2017-10-04 Thread pkg at 1tein dot de 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80865

--- Comment #6 from Christian Cornelssen  ---
Created attachment 42304
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42304&action=edit
Patchset 2 from patch-darwin-ppc-2017-01-msg02971.diff, sufficient for non-Ada
builds to succeed

[Bug target/80865] broken compilation on Mac OS X 10.5 / powerpc: unrecognizable insn

2017-10-04 Thread pkg at 1tein dot de 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80865

--- Comment #7 from Christian Cornelssen  ---
I have made the time-consuming effort of building and testing gcc-7.2.0 with
varying subsets of the four patchsets proposed with attachment 42124.

* Patchset 1/4 copies stack alignment changes previously applied to aix.h.
  This seems to cause 15 additional testsuite failures
  involving gcc/testsuite/gcc.dg/builtin-apply4.c and
  gcc/testsuite/gcc.dg/torture/stackalign/builtin-apply-4.c.
  The failures are related to the builtins around __builtin_apply
  as defined in gcc/builtins.c.
  I'd leave that patchset out.
* Patchset 2/4 turns out to be necessary and sufficient for the non-Ada
  build to succeed. If you want a minimal patchset, stick to that one.
  Given as attachment 42304 now.
* Patchset 3/4 seems reasonable (marking longjmp noreturn),
  but does not contribute changes to the test summary.
* Patchset 4/4 looks reasonable (selecting Darwin thread headers),
  but is Ada-related, thus irrelevant for non-Ada builds.

Attaching the gcc7 testsuite log diff showing the removal of
alignment test failures when only patchset 2 (attachment 42304 instead of
attachment 42124) is used.

[Bug target/80865] broken compilation on Mac OS X 10.5 / powerpc: unrecognizable insn

2017-10-04 Thread pkg at 1tein dot de 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80865

--- Comment #8 from Christian Cornelssen  ---
Created attachment 42305
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42305&action=edit
differences in non-Ada testsuite results when switching from attachment 42124
to attachment 42304

[Bug target/80865] broken compilation on Mac OS X 10.5 / powerpc: unrecognizable insn

2017-10-05 Thread pkg at 1tein dot de 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80865

--- Comment #10 from Christian Cornelssen  ---
(In reply to Iain Sandoe from comment #9)
> > * Patchset 3/4 seems reasonable (marking longjmp noreturn),
> >   but does not contribute changes to the test summary.
> 
> Are you building Fortran?

Yes. I use the MacPorts setup which sets

--enable-languages=c,c++,objc,obj-c++,lto,fortran

> IIRC, that patch was required for Fortran bootstrap to complete.

Well, my testsuite runs are based on the GCC-7.2.0 release, plus some or all of
the patches in attachment 42124.

> > * Patchset 4/4 looks reasonable (selecting Darwin thread headers),
> >   but is Ada-related, thus irrelevant for non-Ada builds.
> 
> Well, generally I build for all the supported languages including Ada,
> Fortran (and Java where supported) so generally I will keep patches to allow
> all of those to succeed.

That's fine; just keep in mind that the patch has not been covered in my tests
because Ada has not been enabled there. To me, it looks like patch 4 should be
necessary for Darwin 8 (Tiger) and Darwin 9 (Leopard) if Ada is built, but that
is just a guess.