public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/105010] [12 regression] GCC 12 after 20220227 fails to build on powerpc64-freebsd with Error: invalid mfcr mask
Date: Wed, 23 Mar 2022 12:41:32 +0000	[thread overview]
Message-ID: <bug-105010-4-AnEaIT1UNh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105010-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Created attachment 52670
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52670&action=edit
proposed patch

Does this help?  The 7450 (which is what freebsd64 defaults to) indeed does
not support these instructions, and it isn't clear to me why we generate them
at all anyway, but this patch makes us more conservative here still.

  parent reply	other threads:[~2022-03-23 12:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-22  2:50 [Bug bootstrap/105010] New: GCC 12 after 20220227 fails " pkubaj at anongoth dot pl
2022-03-22  8:45 ` [Bug bootstrap/105010] GCC 12 after 20220227 fails to build " rguenth at gcc dot gnu.org
2022-03-22  8:47 ` pkubaj at anongoth dot pl
2022-03-22 10:34 ` [Bug target/105010] [12 regression] " rguenth at gcc dot gnu.org
2022-03-22 20:57 ` pkubaj at anongoth dot pl
2022-03-22 22:50 ` segher at gcc dot gnu.org
2022-03-22 23:00 ` pkubaj at anongoth dot pl
2022-03-23 11:34 ` pkubaj at anongoth dot pl
2022-03-23 12:41 ` segher at gcc dot gnu.org [this message]
2022-03-23 14:54 ` pkubaj at anongoth dot pl
2022-03-23 17:33 ` pkubaj at anongoth dot pl
2022-03-23 18:56 ` segher at gcc dot gnu.org
2022-03-23 21:26 ` pkubaj at anongoth dot pl
2022-03-23 22:33 ` segher at gcc dot gnu.org
2022-03-23 23:26 ` pkubaj at anongoth dot pl
2022-04-04 13:05 ` segher at gcc dot gnu.org
2022-04-06 21:28 ` bergner at gcc dot gnu.org
2022-05-06  8:33 ` [Bug target/105010] [12/13 " jakub at gcc dot gnu.org
2022-12-31  4:26 ` pkubaj at anongoth dot pl
2022-12-31 18:24 ` segher at gcc dot gnu.org
2023-01-01 13:26 ` pkubaj at anongoth dot pl
2023-01-03 23:24 ` segher at gcc dot gnu.org
2023-01-05 14:04 ` pkubaj at anongoth dot pl
2023-01-05 15:03 ` segher at gcc dot gnu.org
2023-02-13 22:39 ` pkubaj at anongoth dot pl
2023-05-08 12:24 ` [Bug target/105010] [12/13/14 " rguenth at gcc dot gnu.org

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-105010-4-AnEaIT1UNh@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).