public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-5324] options: fix cl_target_option_print_diff() with strings
Date: Tue, 24 Jan 2023 10:56:02 +0000 (GMT)	[thread overview]
Message-ID: <20230124105602.634173858D1E@sourceware.org> (raw)

https://gcc.gnu.org/g:9f0cb3368af735e95776769c4f28fa9cbb60eaf8

commit r13-5324-g9f0cb3368af735e95776769c4f28fa9cbb60eaf8
Author: Eric Biggers <ebiggers@google.com>
Date:   Tue Jan 24 11:54:41 2023 +0100

    options: fix cl_target_option_print_diff() with strings
    
    Fix an obvious copy-and-paste error where ptr1 was used instead of ptr2.
    This bug caused the dump file produced by -fdump-ipa-inline-details to
    not correctly show the difference in target options when a function
    could not be inlined due to a target option mismatch.
    
    gcc/ChangeLog:
            PR bootstrap/90543
            * optc-save-gen.awk: Fix copy-and-paste error.
    
    Signed-off-by: Eric Biggers <ebiggers@google.com>

Diff:
---
 gcc/optc-save-gen.awk | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/optc-save-gen.awk b/gcc/optc-save-gen.awk
index e91adf7f132..d2cb53c477f 100644
--- a/gcc/optc-save-gen.awk
+++ b/gcc/optc-save-gen.awk
@@ -1013,7 +1013,7 @@ for (i = 0; i < n_target_string; i++) {
 	print "             indent, \"\",";
 	print "             \"" name "\",";
 	print "             ptr1->x_" name " ? ptr1->x_" name " : \"(null)\",";
-	print "             ptr2->x_" name " ? ptr1->x_" name " : \"(null)\");";
+	print "             ptr2->x_" name " ? ptr2->x_" name " : \"(null)\");";
 	print "";
 }

                 reply	other threads:[~2023-01-24 10:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230124105602.634173858D1E@sourceware.org \
    --to=jakub@gcc.gnu.org \
    --cc=gcc-cvs@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).