Re: [lambda] Segmentation fault in simple lambda program

Jason Merrill wrote: Experimenting with a working version and seeing it's issues will be useful to me. To others to maybe. With concepts gone from C++0x and being reworked for C++15(?) maybe support for polymorphic lambdas could be reintroduced? -- though I'm sure its much too late for that an

Re: [lambda] Segmentation fault in simple lambda program

I haven't been following GCC, so I need to thank Jason for forwarding this issue to me. I just read through the messages on the list, and had some more comments: +/* relayout again -- to allow for implicit + * parameters to have been added to the capture if it was a + * 'default ca

Re: [lambda] Segmentation fault in simple lambda program

Adam Butcher wrote: Hopefully. From my point of view the class generated by a lambda expression should be equivalent to something you could write yourself -- aside from the single stack-pointer reference optimization which only a compiler could achieve -- the class has a name, albeit invisibl

Re: [lambda] Segmentation fault in simple lambda program

Jason Merrill wrote: On 08/04/2009 09:35 AM, John Freeman wrote: In my opinion, lambdas are not intended as just a shortcut to writing a function object class. This is why our proposal did not require that lambdas be implemented as classes; it is simply one implementation. (Awaiting word to

Re: [lambda] Segmentation fault in simple lambda program

Jason Merrill wrote: On 08/04/2009 10:17 AM, John Freeman wrote: Reiterating, to allow more freedom in implementation, we can just say it "behaves as" a template, rather than "is" a template. I don't see the difference. As long as they work the same, the compiler

Re: [lambda] Segmentation fault in simple lambda program

Jason Merrill wrote: Incidentally, how does it work to just move the existing call of finish_struct to after we parse the body? I don't see why we need it to be complete while we're in the body. When I was working on it, there were some checks to make sure the class was complete. I can't re

Re: [lambda] Segmentation fault in simple lambda program

John Freeman wrote: +/* relayout again -- to allow for implicit + * parameters to have been added to the capture if it was a + * 'default capture' -- note that this would not be necessary if + * the stack-pointer variant was implemented -- since the layout +

Re: [lambda] Segmentation fault in simple lambda program

On Thu, Aug 6, 2009 at 6:27 AM, Adam Butcher > wrote: I take you're point on [finish_struct_1] potentially being overkill but at least it means that user programs that copy can work. Right. I only added that comment so that other developers who come along

Re: Transforms on SSA form

There are documented methods of SSA decomposition. The naive method is a simple reversal of SSA composition: SSA composition: rename variables (typically by adding suffix), add phi nodes SSA decomposition: rename variables (by dropping suffix), remove phi nodes The short answer to your quest

Debug build

Howdy, This is something I look into periodically, and each time I find a solution that's slightly better, but not what I want. I've looked at the wiki (http://gcc.gnu.org/wiki/DebuggingGCC) many times, so no need to refer me there. I am trying to debug the C++ front-end, and I took the wik

Re: Debug build

Ian Lance Taylor wrote: John Freeman <[EMAIL PROTECTED]> writes: This is something I look into periodically, and each time I find a solution that's slightly better, but not what I want. I've looked at the wiki (http://gcc.gnu.org/wiki/DebuggingGCC) many times, so no need t

Re: Please, do not use the merged revisions log as the commit message when merging

Christopher Faylor wrote: On Sat, Aug 16, 2008 at 02:35:08PM +0200, Manuel L?pez-Ib??ez wrote: Dear GCC devs, Please do *not* use the full logs of the merged revisions as the commit message of a merge. Apart from making the output of svn log useless, commits messages are parsed are tracked f

Re: Please, do not use the merged revisions log as the commit message when merging

Daniel Berlin wrote: It's listed on the wiki that explains how to maintain branches :) I had no idea such a wiki even existed. It would really help future contributors, I'm sure, if, perhaps during copyright assignment, there were some sort of "introduction" process that clearly communicat

Re: Please, do not use the merged revisions log as the commit message when merging

Christopher Faylor wrote: On Sun, Aug 17, 2008 at 03:01:03PM -0500, John Freeman wrote: Daniel Berlin wrote: It's listed on the wiki that explains how to maintain branches :) I had no idea such a wiki even existed. It would really help future contributors, I'