public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: John David Anglin <danglin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-5560] Fix typo in t-dimode Date: Sat, 27 Nov 2021 21:48:33 +0000 (GMT) [thread overview] Message-ID: <20211127214833.D75303858C3A@sourceware.org> (raw) https://gcc.gnu.org/g:14dd0921fe9ee153de17b3de2786e5588ffdc52a commit r12-5560-g14dd0921fe9ee153de17b3de2786e5588ffdc52a Author: John David Anglin <danglin@gcc.gnu.org> Date: Sat Nov 27 21:47:47 2021 +0000 Fix typo in t-dimode 2021-11-27 John David Anglin <danglin@gcc.gnu.org> libgcc/ChangeLog: * config/pa/t-dimode (lib2difuncs): Fix typo. Diff: --- libgcc/config/pa/t-dimode | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libgcc/config/pa/t-dimode b/libgcc/config/pa/t-dimode index 1344e937644..19252a6e6b1 100644 --- a/libgcc/config/pa/t-dimode +++ b/libgcc/config/pa/t-dimode @@ -1,5 +1,5 @@ # Extra DImode libgcc2 functions to build. -lib2difuncs = _muldi3 _negdi2 _lshrdi _ashldi3 _ashrdi3 _cmpdi2 _ucmpdi2 +lib2difuncs = _muldi3 _negdi2 _lshrdi3 _ashldi3 _ashrdi3 _cmpdi2 _ucmpdi2 # Build lib2difuncs. lib2difuncs-o = $(patsubst %,%_di$(objext),$(lib2difuncs))
reply other threads:[~2021-11-27 21:48 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=20211127214833.D75303858C3A@sourceware.org \ --to=danglin@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).