On Mon, Aug 12, 2013 at 11:04 AM, Anna Tikhonova
wrote:
> Also, there should be an issue with -masm=intel for sse3_monitor. Please see
> attached patch.
We can just use "monitor" with implicit operands here, like in
attached patch. It should handle 32bit, 64bit and x32 targets with ATT
and Intel
On Mon, Aug 12, 2013 at 9:51 PM, Uros Bizjak wrote:
> On Mon, Aug 12, 2013 at 3:39 PM, Perez Read wrote:
>
>> movabs is incorrectly translated into "mov [rax], -1", and causes
>> compile error "Error: ambiguous operand size for `mov' ".
>> It should be "mov QWORD PTR [rax], -1"
>>
On Mon, Aug 12, 2013 at 5:26 PM, Uros Bizjak wrote:
> On Mon, Aug 12, 2013 at 11:24 AM, Perez Read wrote:
>
movabs is incorrectly translated into "mov [rax], -1", and causes
compile error "Error: ambiguous operand size for `mov' ".
It should be "mov QWORD PTR [rax], -1"
B
On Mon, Aug 12, 2013 at 11:24 AM, Perez Read wrote:
>>> movabs is incorrectly translated into "mov [rax], -1", and causes
>>> compile error "Error: ambiguous operand size for `mov' ".
>>> It should be "mov QWORD PTR [rax], -1"
>>>
>>> Bootstrap passed. Regression tested on x86_64-unknown-linux-gn
On Mon, Aug 12, 2013 at 2:52 PM, Uros Bizjak wrote:
> Hello!
>
>> movabs is incorrectly translated into "mov [rax], -1", and causes
>> compile error "Error: ambiguous operand size for `mov' ".
>> It should be "mov QWORD PTR [rax], -1"
>>
>> Bootstrap passed. Regression tested on x86_64-unknown-lin
Hello!
> movabs is incorrectly translated into "mov [rax], -1", and causes
> compile error "Error: ambiguous operand size for `mov' ".
> It should be "mov QWORD PTR [rax], -1"
>
> Bootstrap passed. Regression tested on x86_64-unknown-linux-gnu (pc).
>
> 2013-08-10 Perez Read
>
> * config
When compiles below testcase with gcc -masm=intel -O2
--cut here--
int test(){
long *ptr = (long*)0x8000;
*ptr = -1;
return 0;
}
--cut here--
movabs is incorrectly translated into "mov [rax], -1", and causes
compile error "Error: ambiguous operand size for `mov' ".
It sh
