Thanks Joe.
As far as I know the problem I'm seeing isn't a regression but perhaps
this script could still be useful. I don't really understand how it is
supposed to work, since it doesn't appear be working off svn updates.
Should I do something like a binary svn search between revisions
124707 and 132947? It takes such a long amount of time to compile g++,
almost a half an hour with my quad core, that it didn't seem practical
try to do build so many times. I guess there is probably a way to
build g++ without the rest of gcc, but I haven't seen an option for
it.
On Fri, Feb 13, 2009 at 11:22 AM, Joe Buck <joe.b...@synopsys.com> wrote:
> On Fri, Feb 13, 2009 at 08:53:34AM -0800, Anthony Newnam wrote:
>> I asked on gcc-help, but it seems like this list may be more
>> appropriate as it deals with the gcc source.
>>
>> I have noticed that in my g++ <4.3.0, I am able to compile the
>> following code without any errors:
>> struct A;
>> void foo(A);
>> void bar(A* p){foo(*p);}
>>
>> In g++ 4.3.0 this seems to have been fixed, but I'm having a very hard
>> time locating the fix for it. I was hoping that someone could point me
>> in a general direction and hopefully even a changeset. I would like to
>> be able to backport this to g++ 4.1.2 if possible.
>
> It's possible that no one can answer you because this was fixed as a
> side effect of fixing a different problem.
>
> You might have to resort to a binary search through the subversion
> database to find the fix. There's a script in the contrib area of
> the gcc sources called reg_search that can help to automate the
> process. The endpoints for your search would be the point where
> the 4.2 branch was created, and the point where the 4.3 branch was
> created, since the fix must have gone into the trunk sometime between
> those two points.
>
>
>
