public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/94201] aarch64:ICE in tiny code model for ilp32 Date: Wed, 18 Mar 2020 11:50:26 +0000 [thread overview] Message-ID: <bug-94201-4-ge9MZx58tz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94201-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94201 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Sandiford <rsandifo@gcc.gnu.org>: https://gcc.gnu.org/g:d91480dee934478063fe5945b73ff3c108e40a91 commit r10-7240-gd91480dee934478063fe5945b73ff3c108e40a91 Author: Duan bo <duanbo3@huawei.com> Date: Wed Mar 18 10:18:39 2020 +0000 aarch64: Fix SYMBOL_TINY_GOT handling for ILP32 [PR94201] The SYMBOL_TINY_GOT case in aarch64_load_symref_appropriately was missing support for ILP32. This caused an ICE on the testcase. 2020-03-18 Duan bo <duanbo3@huawei.com> gcc/ PR target/94201 * config/aarch64/aarch64.md (ldr_got_tiny): Delete. (@ldr_got_tiny_<mode>): New pattern. (ldr_got_tiny_sidi): Likewise. * config/aarch64/aarch64.c (aarch64_load_symref_appropriately): Use them to handle SYMBOL_TINY_GOT for ILP32. gcc/testsuite/ PR target/94201 * gcc.target/aarch64/pr94201.cï¼New test.
next prev parent reply other threads:[~2020-03-18 11:50 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-17 2:21 [Bug c/94201] New: " duanbo3 at huawei dot com 2020-03-17 6:17 ` [Bug c/94201] " duanbo3 at huawei dot com 2020-03-17 8:18 ` marxin at gcc dot gnu.org 2020-03-18 11:50 ` cvs-commit at gcc dot gnu.org [this message] 2020-03-19 7:42 ` [Bug target/94201] " rsandifo 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-94201-4-ge9MZx58tz@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: 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).