public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "judge.packham at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/105607] sh-unknown-elf: Error: opcode not valid for this cpu variant
Date: Sun, 15 May 2022 08:58:02 +0000	[thread overview]
Message-ID: <bug-105607-4-OSsk7FJyOd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105607-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105607

--- Comment #6 from Chris Packham <judge.packham at gmail dot com> ---
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_BUILD='-O2 -g
-I/home/runner/work/crosstool-ng/crosstool-ng/.build/sh-unknown-elf/buildtools/include
 ' CXXFLAGS='-O2 -g
-I/home/runner/work/crosstool-ng/crosstool-ng/.build/sh-unknown-elf/buildtools/include
  ' CXXFLAGS_FOR_BUILD='-O2 -g
-I/home/runner/work/crosstool-ng/crosstool-ng/.build/sh-unknown-elf/buildtools/include
  '
LDFLAGS='-L/home/runner/work/crosstool-ng/crosstool-ng/.build/sh-unknown-elf/buildtools/lib
 ' CFLAGS_FOR_TARGET='-g -O2  -idirafter
/home/runner/work/crosstool-ng/crosstool-ng/x-tools/sh-unknown-elf/sh-unknown-elf/include'
CXXFLAGS_FOR_TARGET='-g -O2  -idirafter
/home/runner/work/crosstool-ng/crosstool-ng/x-tools/sh-unknown-elf/sh-unknown-elf/include'
LDFLAGS_FOR_TARGET=' -static' '/usr/bin/bash'
'/home/runner/work/crosstool-ng/crosstool-ng/.build/sh-unknown-elf/src/gcc/configure'
'--build=x86_64-build_pc-linux-gnu' '--host=x86_64-build_pc-linux-gnu'
'--target=sh-unknown-elf'
'--prefix=/home/runner/work/crosstool-ng/crosstool-ng/.build/sh-unknown-elf/buildtools'
'--exec_prefix=/home/runner/work/crosstool-ng/crosstool-ng/.build/sh-unknown-elf/buildtools'
'--with-local-prefix=/home/runner/work/crosstool-ng/crosstool-ng/x-tools/sh-unknown-elf/sh-unknown-elf'
'--without-headers' '--with-newlib' '--enable-threads=no' '--disable-shared'
'--with-endian=little,big' '--with-pkgversion=crosstool-NG UNKNOWN'
'--enable-__cxa_atexit' '--disable-libgomp' '--disable-libmudflap'
'--disable-libmpx' '--disable-libssp' '--disable-libquadmath'
'--disable-libquadmath-support' '--disable-libstdcxx-verbose'
'--disable-libstdcxx'
'--with-gmp=/home/runner/work/crosstool-ng/crosstool-ng/.build/sh-unknown-elf/buildtools'
'--with-mpfr=/home/runner/work/crosstool-ng/crosstool-ng/.build/sh-unknown-elf/buildtools'
'--with-mpc=/home/runner/work/crosstool-ng/crosstool-ng/.build/sh-unknown-elf/buildtools'
'--with-isl=/home/runner/work/crosstool-ng/crosstool-ng/.build/sh-unknown-elf/buildtools'
'--enable-lto' '--enable-target-optspace' '--disable-nls' '--enable-multiarch'
'--enable-languages=c'

incidentally if anyone wants the full log it's downloadable from
https://github.com/crosstool-ng/crosstool-ng/suites/6509540897/artifacts/242118465

  parent reply	other threads:[~2022-05-15  8:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-15  7:10 [Bug libgcc/105607] New: " judge.packham at gmail dot com
2022-05-15  7:21 ` [Bug target/105607] " pinskia at gcc dot gnu.org
2022-05-15  7:34 ` judge.packham at gmail dot com
2022-05-15  8:42 ` judge.packham at gmail dot com
2022-05-15  8:49 ` pinskia at gcc dot gnu.org
2022-05-15  8:56 ` pinskia at gcc dot gnu.org
2022-05-15  8:58 ` judge.packham at gmail dot com [this message]
2022-05-15  9:17 ` judge.packham at gmail dot com
2022-05-15  9:29 ` pinskia at gcc dot gnu.org
2022-05-15 10:00 ` judge.packham at gmail dot com
2022-05-30  6:57 ` judge.packham at gmail dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-105607-4-OSsk7FJyOd@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).