------- Comment #10 from burnus at gcc dot gnu dot org 2009-10-07 08:20 ------- (In reply to comment #8) > Created an attachment (id=18732) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18732&action=view) [edit] > Potential patch to fix pr40737 > > Here is a patch from Adhemerval Zanella from our IBM LTC Performance team, > that "fixes" the problem for me and bootstraps (powerpc64-linux) and > regtests with no regressions. Can someone else give this a try on their > system?
I think it only paper bags the problem. The problem is that the span information needs to be available in all places where the pointer is available - also if the module a separate file from the one where the assignment is done which can be again separate from the place where the pointer is used. Thus, as written, I only see two solutions: Solution 1: Always create that variable if they symbols is a pointer to an array. Solution 2: Defer it until we have the proper array descriptor, which handles this. I think in 4.6 we will finally go for solution 2. Nevertheless, one should check whether the patch improves the situation for 4.5 and should thus be applied as interim solution. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40737
