public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/64688] [5 Regression] internal compiler error: Max. number of generated reload insns per insn is achieved (90)
Date: Wed, 21 Jan 2015 20:52:00 -0000 [thread overview]
Message-ID: <bug-64688-4-gfh4pK4Dtb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64688-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64688
--- Comment #3 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #2)
> This is while reloading
> (define_insn "vec_set<mode>_0"
> [(set (match_operand:VI4F_128 0 "nonimmediate_operand"
> "=Yr,*v,v,v ,x,x,v,Yr ,*x ,x ,m ,m ,m")
> (vec_merge:VI4F_128
> (vec_duplicate:VI4F_128
> (match_operand:<ssescalarmode> 2 "general_operand"
> " Yr,*v,m,*r,m,x,v,*rm,*rm,*rm,!x,!*re,!*fF"))
> (match_operand:VI4F_128 1 "vector_move_operand"
> " C , C,C,C ,C,0,v,0 ,0 ,x ,0 ,0 ,0")
> (const_int 1)))]
> instruction I think.
The problem is related to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64477
The solution proposed there solves this problem too. Changing '*r' to 'r"
resulting in constraint
" Yr,*v,m,r,m,x,v,*rm,*rm,*rm,!x,!*re,!*fF"
will solve the PR. So the change will solve 2 PRs (this one and 64477).
I believe it is up to x86 maintainers to do this change.
next prev parent reply other threads:[~2015-01-21 20:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 12:34 [Bug target/64688] New: " trippels at gcc dot gnu.org
2015-01-20 16:50 ` [Bug target/64688] [5 Regression] " jakub at gcc dot gnu.org
2015-01-21 20:52 ` vmakarov at gcc dot gnu.org [this message]
2015-01-22 8:09 ` ubizjak at gmail dot com
2015-01-22 14:45 ` uros at gcc dot gnu.org
2015-01-22 20:26 ` uros at gcc dot gnu.org
2015-01-23 23:05 ` jakub at gcc dot gnu.org
2015-01-24 10:31 ` trippels at gcc dot gnu.org
2015-01-24 10:40 ` trippels at gcc dot gnu.org
2015-01-24 10:42 ` ubizjak at gmail dot com
2015-01-24 14:40 ` trippels at gcc dot gnu.org
2015-01-25 16:00 ` [Bug rtl-optimization/64688] " ubizjak at gmail dot com
2015-01-30 22:23 ` [Bug rtl-optimization/64688] [4.9/5 " vmakarov at gcc dot gnu.org
2015-01-31 2:48 ` law at redhat dot com
2015-01-31 7:18 ` trippels at gcc dot gnu.org
2015-01-31 8:53 ` [Bug rtl-optimization/64688] [4.9 " jakub at gcc dot gnu.org
2015-02-03 16:31 ` law at redhat dot com
2015-02-04 18:26 ` vmakarov at gcc dot gnu.org
2015-03-27 20:13 ` vmakarov at gcc dot gnu.org
2015-04-22 12:02 ` jakub at gcc dot gnu.org
2015-04-22 12:22 ` 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-64688-4-gfh4pK4Dtb@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).