Actually, according to the C++ standard, 14.7 clause 5 says: - an explicit instantiation definition shall appear at most once in a program
So the example I gave is ill-formed, and armel is probably the one making a useful and correct optimisation based on that. C++ also says we aren't required to issue a diagnostic for this error - so strictly speaking I guess neither behaviour is a bug in gcc at all, unless upstream want to minimise the divergence between how code is handled on different arches. Sorry for the noise, if you don't think this is something upstream should or would care to know about, then you're welcome to close it. Ron -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101226082944.gi2...@audi.shelbyville.oz
