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 10:00:23 +0000	[thread overview]
Message-ID: <bug-105607-4-Cz5WH1Ff3r@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 #9 from Chris Packham <judge.packham at gmail dot com> ---
(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
> 
> That should not have an effect on the multi-libs compiled for.

Indeed. I reverting it with no change.

I don't know anything about the SH architecture so I can't say if -mb -m1 is a
valid combination. But under GCC 11.3.0 it isn't in the default multilib list
but somehow it is under GCC 12.1.0

  parent reply	other threads:[~2022-05-15 10:00 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
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 [this message]
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-Cz5WH1Ff3r@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).