Unexpected output constraints

2010-04-01 Thread Daniel Jacobowitz
I'm debugging a Thumb-2 glibc build failure on trunk for arm-none-linux-gnueabi. I believe it's from Richard Earnshaw's 2010-02-01 patch for TLS patterns, which includes this: (define_insn tls_load_dot_plus_four [(set (match_operand:SI 0 register_operand =l,r) (mem:SI (unspec:SI

Re: Unexpected output constraints

2010-04-01 Thread Bernd Schmidt
On 04/01/2010 10:54 PM, Daniel Jacobowitz wrote: I'm debugging a Thumb-2 glibc build failure on trunk for arm-none-linux-gnueabi. I believe it's from Richard Earnshaw's 2010-02-01 patch for TLS patterns, which includes this: (define_insn tls_load_dot_plus_four [(set (match_operand:SI 0

Re: Unexpected output constraints

2010-04-01 Thread Daniel Jacobowitz
On Fri, Apr 02, 2010 at 12:06:28AM +0100, Bernd Schmidt wrote: On 04/01/2010 10:54 PM, Daniel Jacobowitz wrote: I'm debugging a Thumb-2 glibc build failure on trunk for arm-none-linux-gnueabi. I believe it's from Richard Earnshaw's 2010-02-01 patch for TLS patterns, which includes this:

Re: Unexpected output constraints

2010-04-01 Thread Bernd Schmidt
On 04/01/2010 11:08 PM, Daniel Jacobowitz wrote: (define_insn tls_load_dot_plus_four [(set (match_operand:SI 0 register_operand =l,r) (mem:SI (unspec:SI [(match_operand:SI 1 register_operand l,r) (const_int 4) (match_operand 2

Re: Unexpected output constraints

2010-04-01 Thread Daniel Jacobowitz
On Fri, Apr 02, 2010 at 12:27:33AM +0100, Bernd Schmidt wrote: That doesn't work either, a matching constraint has to be an input. i386 uses this, so I figure it's OK. Also, legitimize_tls_address is calling it with the same reg for both operands, which is going to lead to tears if they're