This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
I'm now using a variable length data structure for Q_E_Name as suggested by Robert Dewar. Also I've added a -multi option to gnatmake to switch on the multi source compile mode. This allows test driving the new feature. I plan to send my next patch to gcc-patches and appreciate any comments you may have. Thanks, Oliver On Sat, 2009-05-09 at 16:08 -0400, Robert Dewar wrote: > Oliver Kellogg wrote: > > On 2009-05-04, at 07:36 +0200, Oliver Kellogg wrote: > >> Robert Dewar wrote: > >>>>>>> How about not doing the name expansion in-place but rather > >>>>>>> storing the expanded name in an extra node field? > >>> You could have a separate vector for expanded names I suppose ... > >> So be it. I will change the code to not overwrite the Name field > >> with the expanded name but rather store the expanded name in a > >> data structure separate from the Node. > >> > > > > Luckily, this change was limited to the Exp_Dbug package body. > > FYI I am appending the diff. > > The new Q_E_Name array holds the Name_Id for the expanded name > > of a given entity. The implementation as a fixed array is > > preliminary and I would appreciate suggestions on a better > > data structure to use. > > use a table .. we never use fixed length arrays in the compiler
Attachment:
gnat1_multi_source_compile-2.diff.gz
Description: GNU Zip compressed data
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |