On Wednesday 24 February 2010 18:47:19 Dan Gohman wrote:> SDUse's Prev and Next members implement a use list. Copying them > probably wouldn't immediately break anything, but it wouldn't be > meaningful.I understand that the copied SDUse wouldn't be represented in the list, so I can understand the general reasons for making the copy constructor private. In this case, however, it _may_ be ok. I need to analyze this a bit more. If I can come up with a solution that doesn't require a copy constructor I will of course use that. I can't get a reduced testcase that breaks on trunk but I do have some debug asserts that I'll try on trunk and see if I can get something to fail. There's an iterator issue with ReplaceAllUsesOf. -Dave
I have seen some re-factoring work done to prepare for AVX support. What are the plans (time wise) to add the AVX patterns to the backend? Has anyone thought about FMA4? - Jan
On Thursday 25 February 2010 15:33:58 Jan Sjodin wrote:> I have seen some re-factoring work done to prepare for AVX support. What > are the plans (time wise) to add the AVX patterns to the backend? Has > anyone thought about FMA4?Oh yes. :) FMA4 will have a different feature bit than AVX or FMA3. FMA4 is our top priority after AVX due to Bulldozer. What would you like to see for FMA4? I will be implementing that just as soon as I push up some more AVX support. The AVX work is ready to be pushed up and I am working on that. Unfortunately, pesky things like software releases are getting in the way. :) I hope to get back to this next week. -Dave