Committed the attached change to trunk and 4.7 after testing on hppa-
unknown-linux-gnu.
Working on a revised change for 4.6.
I don't think symbol + constant can occur but I'm not absolutely sure.
On 2-Jan-13, at 8:12 AM, Richard Sandiford wrote:
In any case, reload needs to know up-front tha
David Edelsohn writes:
> The testcase should have included dg-add-options tls. committed as obvious.
Thanks. I also removed the main point of the test in a final "tweak".
Also committed as obvious after testing on mips64-linux-gnu.
Richard
gcc/testsuite/
* gcc.dg/torture/tls/tls-reloa
The testcase should have included dg-add-options tls. committed as obvious.
Index: tls-reload-1.c
===
--- tls-reload-1.c (revision 194830)
+++ tls-reload-1.c (working copy)
@@ -1,5 +1,6 @@
/* { dg-do run } */
/* { dg-requ
Richard Henderson writes:
> On 01/02/2013 05:12 AM, Richard Sandiford wrote:
>> * gcc.dg/torture/tls/tls-reload-1.c: New test.
>
> Ok.
Thanks, committed. And sorry for not volunteering a patch for the x86 ICE,
but I barely know the port...
Richard
On 01/02/2013 05:12 AM, Richard Sandiford wrote:
> * gcc.dg/torture/tls/tls-reload-1.c: New test.
Ok.
r~
John David Anglin writes:
> The attached change fixes PR target/5379. ICE occurs when reload tries
> to emit a move instruction containing a TLS symbol reference as the source
> operand. This requires several scratch registers. As a result, it isn't
> possible for a reload pattern to handle thi
The attached change fixes PR target/5379. ICE occurs when reload tries
to emit a move instruction containing a TLS symbol reference as the source
operand. This requires several scratch registers. As a result, it isn't
possible for a reload pattern to handle this case. So, the best solution
was
