Das, Dibyendu wrote: > I have seen similar issues while trying to fix a memory overflow error while > compiling one of the newer CPUv6 C++ bms, where cc1plus42 consumes quite a > bit of time. > > -Dibyendu > AMD Open64 Compiler Dev > Does valgrind report any leaks? I've not had a chance to look into this yet and if you could share more details it's appreciated. (cc1plus42 vs psclang is like 400M vs 60M.. it's really a huge difference in memory consumed for doing almost the same thing..)
fwiw.. I don't see any memory overflow errors in the compiler.. We've tested against some really evil code that makes "be" consume 15G of memory, but it never died. (Technically it died on a system without enough ram, but I don't blame the compiler for that) I don't know if your boss would give permission, but I'm happy to help you get setup with path64 or EKOPath 4 to test if the problem exists in both codebases. Are you doing an exhaustive search for flag combinations or which flags are you using? ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Open64-devel mailing list Open64-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/open64-devel
