As Bob Paddock wrote: > > As it's a GCC bug which has already been fixed there, and it only > > produces a warning
> It makes C++ code unusable if the local policy is zero tolerance for > warnings. Then either don't use C++, or change that policy (it would suffice to allow "blessed" warnings, based on some peer review), or simply use a compiler version that has the fix applied. No reason for an avr-libc hack. OK, if you are in such an environment, and really feel a hack like this were appropriate, go ahead, and hack up your local avr-libc tree. Your fictitious local zero tolerance policy is not enough convincing to me to poison the official avr-libc with such a hack. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) _______________________________________________ AVR-libc-dev mailing list AVR-libc-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/avr-libc-dev
