Displaying 3 results from an estimated 3 matches for "8ecf9d".
2013 Sep 21
2
[LLVMdev] Debug info failing in assembler.
...# Address Size (in bytes)
.byte 0 # Segment Size (in bytes)
.byte 255
.byte 255
.byte 255
.byte 255
.long comm
.Lset0 = .L.bss_end-comm
.long .Lset0
The typical error message is:
/tmp/debug-8ecf9d.s: Assembler messages:
/tmp/debug-8ecf9d.s: Error: invalid operands (.bss and *COM* sections)
for `-' when setting `.Lset0'
Is it legal to mix .comm symbols and .bss symbols in assembly? Is the
x86 success a bug or a feature?
-Rich
2013 Sep 21
0
[LLVMdev] Debug info failing in assembler.
....byte 0 # Segment Size (in bytes)
> .byte 255
> .byte 255
> .byte 255
> .byte 255
> .long comm
> .Lset0 = .L.bss_end-comm
> .long .Lset0
>
> The typical error message is:
> /tmp/debug-8ecf9d.s: Assembler messages:
> /tmp/debug-8ecf9d.s: Error: invalid operands (.bss and *COM* sections) for
> `-' when setting `.Lset0'
>
> Is it legal to mix .comm symbols and .bss symbols in assembly? Is the x86
> success a bug or a feature?
>
> -Rich
> ___________________...
2013 Sep 22
1
[LLVMdev] Debug info failing in assembler.
....byte 0 # Segment Size (in bytes)
> .byte 255
> .byte 255
> .byte 255
> .byte 255
> .long comm
> .Lset0 = .L.bss_end-comm
> .long .Lset0
>
> The typical error message is:
> /tmp/debug-8ecf9d.s: Assembler messages:
> /tmp/debug-8ecf9d.s: Error: invalid operands (.bss and *COM* sections)
> for `-' when setting `.Lset0'
>
> Is it legal to mix .comm symbols and .bss symbols in assembly? Is the
> x86 success a bug or a feature?
>
> -Rich
> _________________...