This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [patch i386]: Fix sibcall failures caused by allowing constant memories

From: Jeff Law <law at redhat dot com>
To: Kai Tietz <ktietz70 at googlemail dot com>, GCC Patches <gcc-patches at gcc dot gnu dot org>
Cc: Richard Henderson <rth at redhat dot com>, Uros Bizjak <ubizjak at gmail dot com>
Date: Sat, 31 May 2014 14:17:27 -0600
Subject: Re: [patch i386]: Fix sibcall failures caused by allowing constant memories
Authentication-results: sourceware.org; auth=none
References: <CAEwic4at+b8gp_Jdn2_bv3BS3ciixxkq4Zqm-YqunC8SfJ7JfA at mail dot gmail dot com>

On 05/31/14 06:27, Kai Tietz wrote:

Hello,

I resend patch within new thread.
Recent fallout about sibcall was caused by using 'm' constraint for
sibcalls.  By this wrongly combines happened on reload-pass. That
patch introduces new constraint 'B' for sibcall_memory_operand.

ChangeLog

2014-05-31  Kai Tietz  <ktietz@redhat.com>

     * constrains.md (define_constrain): New 'B' constraint.
     * i386.md (sibcall_insn_operand): Use B instead of m constraint.

ChangeLog testsuite

2014-05-31  Kai Tietz  <ktietz@redhat.com>

     * gcc.target/i386/sibcall-6.c: New test.

Bootstrapped i386-unknown-linux-gnu, x86_64-unknown-linux-gnu.  Ok for apply?

OK.
Jeff

References:
- [patch i386]: Fix sibcall failures caused by allowing constant memories
  - From: Kai Tietz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]