search for: assemble_string

...section. */ void go_write_export_data (const char *bytes, unsigned int size) { static section* sec; if (sec == NULL) { gcc_assert (targetm_common.have_named_sections); sec = get_section (".go_export", SECTION_DEBUG, NULL); } switch_to_section (sec); assemble_string (bytes, size); } So you might want to check if copying .go_export sections from the GCC compiled assembler file into the dragonegg compile assembler files suddenly causes Go programs to start working. Ciao, Duncan.

Hi! I've been working on coroutines for some time, and it seems you were right - it makes much more sense to have regular C (and assembly) code for handling coroutines. For instance, I'd otherwise would have to make an assumption about the threading model the platform has (or assume there are no threads at all, which prevents me from allowing goroutine like ("run parallel till you

...tes, unsigned int size) > { > static section* sec; > > if (sec == NULL) > { > gcc_assert (targetm_common.have_named_sections); > sec = get_section (".go_export", SECTION_DEBUG, NULL); > } > > switch_to_section (sec); > assemble_string (bytes, size); > } :-( Fixing things like this was fairly painful in the past. It is sad to see new cases showing up. > So you might want to check if copying .go_export sections from the GCC compiled > assembler file into the dragonegg compile assembler files suddenly causes Go > pro...