public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/50788] [4.7 Regression] ICE: in merge_overlapping_regs, at regrename.c:318 with -mavx -fpeel-loops -fstack-protector-all and __builtin_ia32_maskloadpd256
Date: Sun, 23 Oct 2011 11:28:00 -0000 [thread overview]
Message-ID: <bug-50788-4-m6tRFMeNOh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50788-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50788
--- Comment #6 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2011-10-23 11:27:22 UTC ---
> It is OK for expanders to have match_dup. We just don't want to have
> post-reload passes to trip on double-output to the same register.
No disagreement. I just wanted to state the argument for the + approach, but
the manual clearly points to the match_operand approach here instead.
> BTW: There is another spot with similar problem:
>
> @@ -8011,7 +8011,8 @@
> [(set (mem:V16QI (match_operand:P 0 "register_operand" "D"))
> (unspec:V16QI [(match_operand:V16QI 1 "register_operand" "x")
> (match_operand:V16QI 2 "register_operand" "x")
> - (mem:V16QI (match_dup 0))]
> + (mem:V16QI
> + (match_operand:P 3 "register_operand" "0"))]
> UNSPEC_MASKMOV))]
> "TARGET_SSE2"
> "%vmaskmovdqu\t{%2, %1|%1, %2}"
>
> While compilation won't break here, IMO we should tell the reload that we have
> matching constraint.
Indeed.
next prev parent reply other threads:[~2011-10-23 11:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-19 4:45 [Bug target/50788] New: " zsojka at seznam dot cz
2011-10-19 8:12 ` [Bug rtl-optimization/50788] " rguenth at gcc dot gnu.org
2011-10-21 15:05 ` ebotcazou at gcc dot gnu.org
2011-10-21 15:08 ` ebotcazou at gcc dot gnu.org
2011-10-22 20:42 ` [Bug target/50788] " ebotcazou at gcc dot gnu.org
2011-10-23 8:20 ` ubizjak at gmail dot com
2011-10-23 11:00 ` ubizjak at gmail dot com
2011-10-23 11:28 ` ebotcazou at gcc dot gnu.org [this message]
2011-10-23 11:46 ` ubizjak at gmail dot com
2011-10-23 13:06 ` ubizjak at gmail dot com
2011-10-23 13:44 ` ubizjak at gmail dot com
2011-10-23 14:18 ` uros at gcc dot gnu.org
2011-10-23 15:16 ` uros at gcc dot gnu.org
2011-10-23 15:17 ` uros at gcc dot gnu.org
2011-10-23 15:19 ` uros at gcc dot gnu.org
2011-10-23 15:20 ` ubizjak at gmail dot com
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-50788-4-m6tRFMeNOh@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: link
Be 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).