public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: "Kewen.Lin" <linkw@linux.ibm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	David Edelsohn <dje.gcc@gmail.com>,
	 Bill Schmidt <wschmidt@linux.ibm.com>,
	Peter Bergner <bergner@linux.ibm.com>
Subject: Re: [PATCH v2] rs6000: Disable MMA if no VSX support [PR103627]
Date: Mon, 7 Feb 2022 02:35:51 -0600	[thread overview]
Message-ID: <20220207083551.GI614@gate.crashing.org> (raw)
In-Reply-To: <cb287def-0880-90c5-5527-fcceca4aa1b2@linux.ibm.com>

On Mon, Feb 07, 2022 at 01:54:00PM +0800, Kewen.Lin wrote:
> on 2022/1/28 上午1:17, Segher Boessenkool wrote:
> > On Thu, Jan 27, 2022 at 07:21:33PM +0800, Kewen.Lin wrote:
> >> 	PR target/103627
> >> 	* config/rs6000/rs6000.cc (rs6000_option_override_internal): Disable
> >> 	MMA if !TARGET_VSX.
> >>
> >> gcc/testsuite/ChangeLog:
> >>
> >> 	PR target/103627
> >> 	* gcc.target/powerpc/pr103627-1.c: New test.
> >> 	* gcc.target/powerpc/pr103627-2.c: New test.
> > 
> > Okay for trunk.  Thanks!
> 
> Thanks Segher!  Commit it as r12-7078 and its successor as r12-7079.
> 
> Since it's related to MMA support, I guess we want to backport it?

Probably, yes.  (Not because it is related to MMA, but more because the
ICE will also exist on older compilers).

> If so, is it ok to backport to GCC 10 and 11 after one week or so?

Okay.  Thanks!


Segher

      reply	other threads:[~2022-02-07  8:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27 11:21 Kewen.Lin
2022-01-27 17:17 ` Segher Boessenkool
2022-02-07  5:54   ` Kewen.Lin
2022-02-07  8:35     ` Segher Boessenkool [this message]

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=20220207083551.GI614@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=bergner@linux.ibm.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=linkw@linux.ibm.com \
    --cc=wschmidt@linux.ibm.com \
    /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).