GCC Status Report (2004-09-13) [--enable-mapped-location]

[Per Bothner]

Mark Mitchell wrote:

> September 19
> 
> * Fix/finish --enable-mapped-location [Bothner]

I have a patch that looks pretty good - it actually does better
on the libjava testsuite than unmodified testsuite (without
--enable-mapped-location) from a few days ago.  I.e. comparing
apples to oranges, but I have limited testing capacity.  I'll
ask for help in a following message.

As a "side effect" I essentially rewrote the Java lexer.  Not from
scratch of course, but lots of moving code around and simplifying
the code paths and data structures.  I'll also be asking people for
help on running some timing tests.

There are a few minor known unfinished pieces that are not
show-stoppers, plus I need to write ChangeLog entries.  Otherwise
(modulo testing and timing) I think its ready.  Unfortuantely, I'm
heading off for vacation/travelling for a week, but supposedly I'll
have WiFi access for most of the time (and I'll be treating it as a
working vacation).

That brings us to the Big Question: with C, C++, Fortran, Java, and
Objc (I think - needs testing) all handling --enable-mapped-location,
we may consider making it the default for 4.0.  (Converting Ada is
not done, but it doesn't look like a major job.)  That assumes I get
help fixing a few minor regressions.  The advantage of doing that is
of course is that we don't have to fight against with rot with
--enable-mapped-location.  Since I have limited volunteer time to
spend on Gcc, I really don't want to be responsible for making
sure other people's check-ins don't break --enable-mapped-location
for as long as stage3 lasts.
-- 
	--Per Bothner
per@bothner.com   http://per.bothner.com/