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 target/112804] ICE in aarch64 crosscompiler in plus_constant, at explow.cc:102 with -mabi=ilp32 and -finline-stringops Date: Mon, 11 Dec 2023 18:32:35 +0000 [thread overview] Message-ID: <bug-112804-4-p1LVAJMl6l@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112804-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112804 --- Comment #3 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Alexandre Oliva <aoliva@gcc.gnu.org>: https://gcc.gnu.org/g:76ca5ab4ef95c41c1ed67edfb34a1a455a602192 commit r14-6429-g76ca5ab4ef95c41c1ed67edfb34a1a455a602192 Author: Alexandre Oliva <oliva@adacore.com> Date: Mon Dec 11 15:09:22 2023 -0300 -finline-stringops: don't assume ptr_mode ptr in memset [PR112804] On aarch64 -milp32, and presumably on other such targets, ptr can be in a different mode than ptr_mode in the testcase. Cope with it. for gcc/ChangeLog PR target/112804 * builtins.cc (try_store_by_multiple_pieces): Use ptr's mode for the increment. for gcc/testsuite/ChangeLog PR target/112804 * gcc.target/aarch64/inline-mem-set-pr112804.c: New.
next prev parent reply other threads:[~2023-12-11 18:32 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-01 8:08 [Bug target/112804] New: ICE in aarch64 crosscompiler in plus_constant, at explow.cc:102 fkastl at suse dot cz 2023-12-01 8:20 ` [Bug target/112804] ICE in aarch64 crosscompiler in plus_constant, at explow.cc:102 with -mabi=ilp32 pinskia at gcc dot gnu.org 2023-12-09 2:59 ` [Bug target/112804] ICE in aarch64 crosscompiler in plus_constant, at explow.cc:102 with -mabi=ilp32 and -finline-stringops aoliva at gcc dot gnu.org 2023-12-11 18:32 ` cvs-commit at gcc dot gnu.org [this message] 2023-12-11 18:46 ` aoliva at gcc dot gnu.org 2024-01-04 15:45 ` fkastl at suse dot cz 2024-01-20 17:25 ` pinskia 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-112804-4-p1LVAJMl6l@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).