On Wed, Jul 11, 2012 at 5:03 AM, Vinh Nguyen <vinhdi...@gmail.com> wrote: >> That said, it very much looks like an issue with g++ 4.7.*. I actually made a >> small change to make it work at my end (Debian testing, g++-4.7.1). >> > > Yes, g++ 4.7.* was used...
GCC versions 4.7.0 and 4.7.1 are full of bugs within the C++ compiler. I wouldn't trust GCC 4.7 until version 4.7.3. There is a bazillion bug reports on the GCC bug mailing list, all related to GCC 4.7.x: http://gcc.gnu.org/ml/gcc-bugs/ Perhaps the amount of bugs being reported has a correlation with the amount of crack smoked by GCC developers. Following this line of thought, perhaps the amount of crack being smoked is directly proportional to the amount of memory loss, making the developers forget the golden rules of development: "adding new features = adding new tests" and "adding new features = test if new features break existing code". However, if we apply this perfectly logical correlation to its full conclusion, it would indicate that other software "makers", such as Microsuck, have industrial strength meth labs on premises, with MS employees getting free crystal meth along with their corn flakes as morning breakfast. The horrible state of the Visual C++ compiler (as well as other Microsuck software) makes GCC look like utmost perfection, created by aliens that are 1000 years more advanced than us. One known GCC bug directly relevant to us is: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53549 I've made a workaround for this bug in Armadillo 3.2.4, at the trade-off of losing a small amount of functionality. _______________________________________________ Rcpp-devel mailing list Rcpp-devel@lists.r-forge.r-project.org https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
