> -----Original Message----- > From: Boyapati, Anitha > Sent: Tuesday, November 09, 2010 1:57 AM > To: avr-libc-dev@nongnu.org; Weddington, Eric > Subject: FW: [avr-libc-commit] [2191] 2010-11-05 Eric B. > > > Hi, > > > I just saw the committed changes. To avoid the compilation > errors, !defined(__AVR_TINY__) is included in almost all libc > and libm files. > > I am not sure if this is already discussed but going forward, > when AVR tiny is supported in future, should the developer > undo these changes? To me this looks repetitive and not so modular. > > If possible modifying build scripts for Tiny target is a much > better alternative. Thoughts? >
Well, certainly the point is to eventually support the Tiny10 family some time in the future. When that happens, each function will have to be done on a case-by-case basis. Some functions can be modified with just register changes. Some can be modified with just a macro to substitute different, small assembly sequences. Or even both these methods. In those cases, the conditional compilation will go away. In other cases, the whole algorithm may have to be modified and there may need to be conditional compilation. The point is that all of the conditional compilation I put in is temporary until the Tiny10 family is correctly supported. It doesn't have to look pretty. It just has to get avr-libc to a point where it can be built without using make -k. Patches welcome. _______________________________________________ AVR-libc-dev mailing list AVR-libc-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/avr-libc-dev
