Thanks for the tip Than. You are helping me understand this bit by bit ;)

I'm guessing I have to adjust these portions (if no specific gccgo build 
tag is available)?

Best,
Benedikt

On Wednesday, December 19, 2018 at 3:05:08 PM UTC+1, Than McIntosh wrote:
>
>  On Wed, Dec 19, 2018 at 8:52 AM Benedikt T <ben...@gmail.com 
> <javascript:>> wrote:
>
>> Okay, I moved the multiline definitions into one line respectively, which 
>> solved some of the errors. So this seems to be in fact related to how the 
>> file is being handled by the assembler. Now I still need to fix the 
>> following errors:
>>
>
> What you are seeing is expected behavior -- this is an assembly file 
> written in the syntax accepted by the main Go compiler, whereas gccgo and 
> gollvm require that assembly files use the syntax of the host or system 
> assembler ("as"). 
>
> Typically folks address this by using build tags, e.g. "build !gccgo" in 
> the GC-style assembly source, then a "build +gccgo" in a generic version or 
> gollvm- or gccgo- specific version.
>
> Regards, Than
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to