Displaying 3 results from an estimated 3 matches for "x86_64run".
Did you mean:
x86_64rpm
2013 Sep 21
2
[LLVMdev] Debug info failing in assembler.
...-g -o %t %s && %microblazerun %t
// FAIL: %mipsecc -g -o %t %s && %mipsrun %t
// FAIL: %mipselecc -g -o %t %s && %mipselrun %t
// FAIL: %ppcecc -g -o %t %s && %ppcrun %t
// FAIL: %ppc64ecc -g -o %t %s && %ppc64run %t
// RUN: %x86_64ecc -g -o %t %s && %x86_64run %t
int comm;
int main()
{
comm = 6;
}
This fails on all but the x86 processors. The typical failure looks like
this:
...
.type comm, at object # @comm
.comm comm,4,4
.cfi_sections .debug_frame
.bss
.L.bss_end:
...
.L.debug_abbrev_end:...
2013 Sep 21
0
[LLVMdev] Debug info failing in assembler.
...icroblazerun %t
> // FAIL: %mipsecc -g -o %t %s && %mipsrun %t
> // FAIL: %mipselecc -g -o %t %s && %mipselrun %t
> // FAIL: %ppcecc -g -o %t %s && %ppcrun %t
> // FAIL: %ppc64ecc -g -o %t %s && %ppc64run %t
> // RUN: %x86_64ecc -g -o %t %s && %x86_64run %t
>
> int comm;
> int main()
> {
> comm = 6;
> }
>
> This fails on all but the x86 processors. The typical failure looks like
> this:
> ...
> .type comm, at object # @comm
> .comm comm,4,4
> .cfi_sections .debug_fram...
2013 Sep 22
1
[LLVMdev] Debug info failing in assembler.
...icroblazerun %t
> // FAIL: %mipsecc -g -o %t %s && %mipsrun %t
> // FAIL: %mipselecc -g -o %t %s && %mipselrun %t
> // FAIL: %ppcecc -g -o %t %s && %ppcrun %t
> // FAIL: %ppc64ecc -g -o %t %s && %ppc64run %t
> // RUN: %x86_64ecc -g -o %t %s && %x86_64run %t
>
> int comm;
> int main()
> {
> comm = 6;
> }
>
> This fails on all but the x86 processors. The typical failure looks
> like this:
> ...
> .type comm, at object # @comm
> .comm comm,4,4
> .cfi_sections .debug_fra...