On Jul 19, 2010, at 1:57 PM, Tom Tromey wrote:
> Dave> But yes, OP, it's a long-term project.
>
> Apple implemented fix-and-continue in their toolchain. They spoke about
> it a little bit on the gdb list, it is in the archives. My take-away
> was that the feature is a lot of work for not muc
> "Dave" == Dave Korn writes:
Dave> I think you're probably assuming too much. Tom T. is working on an
Dave> incremental compiler, isn't he?
I was, but I was asked to work on gdb a couple of years ago, so that
work is suspended.
Dave> But yes, OP, it's a long-term project.
Apple impleme
On Sun, Jul 18, 2010 at 14:37, Ian Lance Taylor wrote:
> This idea is related to Tom Tromey's incremental compiler work
> (http://gcc.gnu.org/wiki/IncrementalCompiler) and to Per Bothner's
> compiler server work
> (http://per.bothner.com/papers/GccSummit03-slides/index.html). Neither
> project i
Rick,
You are seeking perfection while I am suggesting a technique that
doesn't capture all
cases but is useful:
1) change only the body of a function
2) compile the new function into a shared library which the
debugger dlopen's
into the target process.
3) replace the entr
On 18 July 2010 23:15, Rick C. Hodgin wrote:
> Jonathan,
>
> If you run Linux, you can download VMware, and install a version of
> Windows XP or later)
I don't have a licence to do that.
> and download Visual Studio Express from Microsoft
> for free. You can experiment with it and see how usefu
Jonathan,
If you run Linux, you can download VMware, and install a version of
Windows XP or later) and download Visual Studio Express from Microsoft
for free. You can experiment with it and see how useful it is. It's
pretty darned amazing actually. Once you use it, you'll always miss it.
Simple
On 18 July 2010 20:52, Rick C. Hodgin wrote:
>
> The idea of having function entry points across the board for all
> executed code would be required, allowing those links to be updated
> dynamically at run-time. We could even use a memory-based lookup table
> that's updated by gdb to the new entry
On Sun, 2010-07-18 at 19:46 +0100, Jonathan Wakely wrote:
> On 18 July 2010 16:25, Rick Hodgin wrote:
> > Ian,
> >
> > The idea is to create a program database of the compiled program on a full
> > compile. Then when asked to re-compile with the edit-and-continue switch,
> > it only looks for cha
Terrence,
Procedure entry points, global and local variable locations in memory,
structure definitions and offsets, etc. These would all have to be
updated as changes are made, and that means each reference used in the
executable would need to be updated, and that could mean several source
files
If you are willing to restrict edit-and-continue to whole procedures
then minimal changes to the compiled
code for procedure entry points is all that is required (well that and
dlopen).
Terrence MIller
On 7/18/2010 12:14 PM, Dave Korn wrote:
On 18/07/2010 16:28, Robert Dewar wrote:
Rick Hodgin writes:
> The idea is to create a program database of the compiled program on a
> full compile. Then when asked to re-compile with the edit-and-continue
> switch, it only looks for changed code and compiles those few
> lines. Everything else it needs to carry out compilation is there
On 18/07/2010 16:28, Robert Dewar wrote:
> Rick Hodgin wrote:
>> Ian,
>>
>> The idea is to create a program database of the compiled program on a
>> full compile. Then when asked to re-compile with the
>> edit-and-continue switch, it only looks for changed code and compiles
>> those few lines. Ever
On 18 July 2010 16:25, Rick Hodgin wrote:
> Ian,
>
> The idea is to create a program database of the compiled program on a full
> compile. Then when asked to re-compile with the edit-and-continue switch, it
> only looks for changed code and compiles those few lines. Everything else it
> needs to
Rick Hodgin wrote:
Ian,
The idea is to create a program database of the compiled program on a
full compile. Then when asked to re-compile with the
edit-and-continue switch, it only looks for changed code and compiles
those few lines. Everything else it needs to carry out compilation is
there fro
Ian,
The idea is to create a program database of the compiled program on a full
compile. Then when asked to re-compile with the edit-and-continue switch, it
only looks for changed code and compiles those few lines. Everything else it
needs to carry out compilation is there from previous full-co
Rick Hodgin writes:
> To my knowledge, GCC does not currently support any edit-and-continue
> abilities. Is this still true? And if so, are there any plans to introduce
> it at some point?
I don't see how it makes sense to add edit-and-continue to gcc.
Compilation times are too slow, but the
16 matches
Mail list logo
