[Bug target/84113] [7/8 Regression] libgcc/unwind.inc:136:1: unrecognizable insn: internal compiler error on Darwin

2018-02-08 Thread mrs at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84113 mrs at gcc dot gnu.org changed: What|Removed |Added Status|ASSIGNED|RESOLVED CC|

[Bug target/84113] [7/8 Regression] libgcc/unwind.inc:136:1: unrecognizable insn: internal compiler error on Darwin

2018-02-08 Thread mrs at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84113 --- Comment #39 from mrs at gcc dot gnu.org --- Author: mrs Date: Thu Feb 8 18:48:37 2018 New Revision: 257501 URL: https://gcc.gnu.org/viewcvs?rev=257501=gcc=rev Log: 2018-02-08 Iain Sandoe PR target/84113

[Bug target/84113] [7/8 Regression] libgcc/unwind.inc:136:1: unrecognizable insn: internal compiler error on Darwin

2018-02-08 Thread mrs at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84113 --- Comment #38 from mrs at gcc dot gnu.org --- Author: mrs Date: Thu Feb 8 18:39:43 2018 New Revision: 257500 URL: https://gcc.gnu.org/viewcvs?rev=257500=gcc=rev Log: Mark previous change with: PR target/84113 Modified:

[Bug target/84113] [7/8 Regression] libgcc/unwind.inc:136:1: unrecognizable insn: internal compiler error on Darwin

2018-02-05 Thread dougmencken at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84113 --- Comment #37 from Douglas Mencken --- (In reply to Segher Boessenkool from comment #36) > I'll take care of it. Fine. I published my build here https://ftp.osuosl.org/pub/manulix/other/GCC/ And they’re on “rs6000” too (; manulix@ftp-osl

[Bug target/84113] [7/8 Regression] libgcc/unwind.inc:136:1: unrecognizable insn: internal compiler error on Darwin

2018-02-05 Thread segher at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84113 Segher Boessenkool changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug target/84113] [7/8 Regression] libgcc/unwind.inc:136:1: unrecognizable insn: internal compiler error on Darwin

2018-02-05 Thread dougmencken at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84113 --- Comment #35 from Douglas Mencken --- (In reply to Douglas Mencken from comment #34) > And this https://gcc.gnu.org/ml/gcc-patches/2018-02/msg00181.html By merging that patch this issue is okay to close as resolved

[Bug target/84113] [7/8 Regression] libgcc/unwind.inc:136:1: unrecognizable insn: internal compiler error on Darwin

2018-02-05 Thread dougmencken at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84113 --- Comment #34 from Douglas Mencken --- And this https://gcc.gnu.org/ml/gcc-patches/2018-02/msg00181.html

[Bug target/84113] [7/8 Regression] libgcc/unwind.inc:136:1: unrecognizable insn: internal compiler error on Darwin

2018-02-05 Thread dougmencken at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84113 --- Comment #33 from Douglas Mencken --- (In reply to Segher Boessenkool from comment #32) > Yes, run "make -k check" (add -jN to taste if you have multiple CPUs). > And then run contrib/test_summary. See if that is as expected (compare > it to

[Bug target/84113] [7/8 Regression] libgcc/unwind.inc:136:1: unrecognizable insn: internal compiler error on Darwin

2018-02-04 Thread segher at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84113 --- Comment #32 from Segher Boessenkool --- Yes, run "make -k check" (add -jN to taste if you have multiple CPUs). And then run contrib/test_summary. See if that is as expected (compare it to previous powerpc-darwin results on gcc-testresults@;

[Bug target/84113] [7/8 Regression] libgcc/unwind.inc:136:1: unrecognizable insn: internal compiler error on Darwin

2018-02-04 Thread dougmencken at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84113 --- Comment #31 from Douglas Mencken --- (In reply to Segher Boessenkool from comment #29) > The patch has never been sent to gcc-patches. It also still never was > properly tested. Can you do that? Or you’re bout sending it to “gcc-patches”

[Bug target/84113] [7/8 Regression] libgcc/unwind.inc:136:1: unrecognizable insn: internal compiler error on Darwin

2018-02-04 Thread dougmencken at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84113 --- Comment #30 from Douglas Mencken --- (In reply to Segher Boessenkool from comment #29) > The patch has never been sent to gcc-patches. It also still never was > properly tested. Can you do that? Like doing ‘make check’ after it completes

[Bug target/84113] [7/8 Regression] libgcc/unwind.inc:136:1: unrecognizable insn: internal compiler error on Darwin

2018-02-04 Thread segher at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84113 --- Comment #29 from Segher Boessenkool --- The patch has never been sent to gcc-patches. It also still never was properly tested. Can you do that?

[Bug target/84113] [7/8 Regression] libgcc/unwind.inc:136:1: unrecognizable insn: internal compiler error on Darwin

2018-02-04 Thread dougmencken at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84113 --- Comment #28 from Douglas Mencken --- (In reply to Segher Boessenkool from comment #27) > Yes. Wow, it compiles So I suggest to push patch https://gcc.gnu.org/ml/gcc-testresults/2017-01/txtnZhWiDkC4z.txt after checking on other rs6000

[Bug target/84113] [7/8 Regression] libgcc/unwind.inc:136:1: unrecognizable insn: internal compiler error on Darwin

2018-02-04 Thread segher at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84113 --- Comment #27 from Segher Boessenkool --- Yes.

[Bug target/84113] [7/8 Regression] libgcc/unwind.inc:136:1: unrecognizable insn: internal compiler error on Darwin

2018-02-04 Thread dougmencken at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84113 --- Comment #26 from Douglas Mencken --- (In reply to Segher Boessenkool from comment #25) > Please test https://gcc.gnu.org/ml/gcc-testresults/2017-01/txtnZhWiDkC4z.txt Okay, and as I got it, it is supposed to apply upon fresh GCC with that

[Bug target/84113] [7/8 Regression] libgcc/unwind.inc:136:1: unrecognizable insn: internal compiler error on Darwin

2018-02-04 Thread segher at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84113 --- Comment #25 from Segher Boessenkool --- Please test https://gcc.gnu.org/ml/gcc-testresults/2017-01/txtnZhWiDkC4z.txt .

[Bug target/84113] [7/8 Regression] libgcc/unwind.inc:136:1: unrecognizable insn: internal compiler error on Darwin

2018-02-04 Thread dougmencken at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84113 --- Comment #24 from Douglas Mencken --- (In reply to Segher Boessenkool from comment #23) > GCC 7 was released more than nine months ago, and yet no one has noticed > that it does not build at all on powerpc-darwin. We cannot do magic. Well,

[Bug target/84113] [7/8 Regression] libgcc/unwind.inc:136:1: unrecognizable insn: internal compiler error on Darwin

2018-02-04 Thread segher at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84113 --- Comment #23 from Segher Boessenkool --- (In reply to Douglas Mencken from comment #22) > as for https://gcc.gnu.org/ml/gcc-patches/2016-08/msg02040.html > I think that optimizing epilogues is a good idea, but not of a cost of >

[Bug target/84113] [7/8 Regression] libgcc/unwind.inc:136:1: unrecognizable insn: internal compiler error on Darwin

2018-02-04 Thread dougmencken at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84113 --- Comment #22 from Douglas Mencken --- So yet I have fully workin’ $ /Developer/GCC/7.3patched/PowerPC/32bit/bin/gcc -v Using built-in specs. COLLECT_GCC=/Developer/GCC/7.3patched/PowerPC/32bit/bin/gcc