This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Tuesday 15 November 2011 04:08:10 Can Finner wrote: > > my first question is, why ? i thought the point of libgloss was to get > > all of the syscall/etc... logic out of newlib completely. the Blackfin > > port works fine and the only code we have in newlib is for handling > > setjmp/longjmp. > > The reason seems that we don't want to break current gcc test procedure. > May be this message could be help. > http://www.cygwin.com/ml/newlib/2011/msg00336.html > > Also, I was not aware of blackfin, how the issue is addressed in blackfin? Blackfin's gcc provides a "-msim" flag which automatically pulls in the additional libs needed (-lsim). then we run the gcc test suite with the -msim compiler flag to link everything, and then run it against the sim to test. if we want to test against hardware, we have linker scripts in libgloss for each of our cpu's, and the -mcpu= option automatically selects the right linker script for that processor, as well as adding the expected libs to link against (-lbfinbsp -lnosys). in all cases, those libs are being generated by libgloss. -mike
Attachment:
signature.asc
Description: This is a digitally signed message part.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |