[Bug target/105607] sh-unknown-elf: Error: opcode not valid for this cpu variant

2022-05-29 Thread judge.packham at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105607 --- Comment #10 from Chris Packham --- I don't know if it helps at all but it looks like we actually noticed the difference between GCC 10 and GCC 11. The workaround we have in ct-ng was GCC 11 specific.

[Bug target/105607] sh-unknown-elf: Error: opcode not valid for this cpu variant

2022-05-15 Thread judge.packham at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105607 --- Comment #9 from Chris Packham --- (In reply to Andrew Pinski from comment #8) > (In reply to Chris Packham from comment #7) > > There's also > > https://gcc.gnu.org/git/?p=gcc.git;a=commit; > > h=081c9dfb67a0d2e7425ddb5420ada588026f92ca > >

[Bug target/105607] sh-unknown-elf: Error: opcode not valid for this cpu variant

2022-05-15 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105607 --- Comment #8 from Andrew Pinski --- (In reply to Chris Packham from comment #7) > There's also > https://gcc.gnu.org/git/?p=gcc.git;a=commit; > h=081c9dfb67a0d2e7425ddb5420ada588026f92ca That should not have an effect on the multi-libs compil

[Bug target/105607] sh-unknown-elf: Error: opcode not valid for this cpu variant

2022-05-15 Thread judge.packham at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105607 --- Comment #7 from Chris Packham --- There's also https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=081c9dfb67a0d2e7425ddb5420ada588026f92ca

[Bug target/105607] sh-unknown-elf: Error: opcode not valid for this cpu variant

2022-05-15 Thread judge.packham at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105607 --- Comment #6 from Chris Packham --- Here's the relevant snippet from the log. CC_FOR_BUILD='x86_64-build_pc-linux-gnu-gcc' CFLAGS='-O2 -g -I/home/runner/work/crosstool-ng/crosstool-ng/.build/sh-unknown-elf/buildtools/include ' CFLAGS_FOR_BUI

[Bug target/105607] sh-unknown-elf: Error: opcode not valid for this cpu variant

2022-05-15 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105607 --- Comment #5 from Andrew Pinski --- The only change I have saw to the sh specific files which would affect was in t-linux but that would be linux only, this is elf. r12-6929-g06995c2958aaae

[Bug target/105607] sh-unknown-elf: Error: opcode not valid for this cpu variant

2022-05-15 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105607 --- Comment #4 from Andrew Pinski --- Can you provide the exact configure options you used?

[Bug target/105607] sh-unknown-elf: Error: opcode not valid for this cpu variant

2022-05-15 Thread judge.packham at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105607 --- Comment #3 from Chris Packham --- Just blindly comparing log files between a good and a bad build the `-mb -m1` combination appears to be new and is the one causing problems.

[Bug target/105607] sh-unknown-elf: Error: opcode not valid for this cpu variant

2022-05-15 Thread judge.packham at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105607 --- Comment #2 from Chris Packham --- binutils is the same but I did update the kernel headers.

[Bug target/105607] sh-unknown-elf: Error: opcode not valid for this cpu variant

2022-05-15 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105607 --- Comment #1 from Andrew Pinski --- >The same configuration/build recipe successfully builds GCC 11.3.0 Did you change binutils too or they kept the same?