From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24695 invoked by alias); 21 Jan 2015 20:52:34 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 24607 invoked by uid 48); 21 Jan 2015 20:52:30 -0000 From: "vmakarov at gcc dot 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vmakarov at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: vmakarov at redhat dot com X-Bugzilla-Target-Milestone: 5.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-01/txt/msg02268.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64688 --- Comment #3 from Vladimir Makarov --- (In reply to Jakub Jelinek from comment #2) > This is while reloading > (define_insn "vec_set_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: 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.