public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/66171] New: [6 Regression]: gcc.target/cris/biap.c Date: Sat, 16 May 2015 02:13:00 -0000 [thread overview] Message-ID: <bug-66171-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66171 Bug ID: 66171 Summary: [6 Regression]: gcc.target/cris/biap.c Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: hp at gcc dot gnu.org CC: vekumar at gcc dot gnu.org Target Milestone: --- Target: cris-elf Before and including r222872, this test passed. After and including r222878, this test fails: Running /tmp/hpautotest-gcc0/gcc/gcc/testsuite/gcc.target/cris/cris.exp ... FAIL: gcc.target/cris/biap.c scan-assembler addi FAIL: gcc.target/cris/biap.c scan-assembler-not lsl A qualified guess is that this is due to r222874. See also PR37939, referenced in the test-case. I'm logging this as target-specific and not a middle-end bug, as the canonical RTL *is* shift, outside of a MEM. More than one pattern to edit: besides changing that multiplication to a shift that need to be taken care of with the canonically stricter RTL, like the side-effect pattern has to be duplicated as noted 6+ years ago in <http://gcc.gnu.org/ml/gcc-patches/2008-11/msg00025.html>. (CC as FYI only.)
next reply other threads:[~2015-05-16 2:13 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-16 2:13 hp at gcc dot gnu.org [this message] 2015-10-16 8:31 ` [Bug target/66171] " rguenth at gcc dot gnu.org 2015-10-16 9:09 ` vekumar at gcc dot gnu.org 2021-02-22 18:11 ` [Bug target/66171] [8/9/10/11 " hp 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-66171-4@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).