This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
> > Everything so far points to the heap not being allocated in the startup > script, crt0.s which we have created for our own crt0 library. How does > gcc handle this when it is a cross compiler? Does the processor need to > be specified on the command line? Heap is normally defined in the Linker script, (__heap_start__ & __heap_end__ ) labels. If I rembeber we had change sbrk (newlib) a bit to get it working porperly. That said we don't use any dynamic memory allocation in our code. Nic ------------------------------------------------- ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |