public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/users/marxin/heads/PR103786-canonical-verifier-bug)] Fix typo in type verification. Date: Tue, 21 Dec 2021 08:50:03 +0000 (GMT) [thread overview] Message-ID: <20211221085003.ACD983858417@sourceware.org> (raw) https://gcc.gnu.org/g:83402bb64929c190fa59600b3eee9a88591921b2 commit 83402bb64929c190fa59600b3eee9a88591921b2 Author: Feng Xue <fxue@os.amperecomputing.com> Date: Tue Dec 21 09:48:16 2021 +0100 Fix typo in type verification. PR ipa/103786 gcc/ChangeLog: * tree.c (verify_type): Fix typo. Diff: --- gcc/tree.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/tree.c b/gcc/tree.c index 72cceda568f..0741e3b01af 100644 --- a/gcc/tree.c +++ b/gcc/tree.c @@ -13530,7 +13530,7 @@ verify_type (const_tree t) tree ct = TYPE_CANONICAL (t); if (!ct) ; - else if (TYPE_CANONICAL (t) != ct) + else if (TYPE_CANONICAL (ct) != ct) { error ("%<TYPE_CANONICAL%> has different %<TYPE_CANONICAL%>"); debug_tree (ct);
reply other threads:[~2021-12-21 8:50 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=20211221085003.ACD983858417@sourceware.org \ --to=marxin@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: linkBe 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).