This is the mail archive of the mailing list for the GDB 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]

Re: Upcoming DWARF 3 and FORTRAN95 patches for 5.1.1 or 5.2?

Hi Daniel,

> > A comment about the patch you mentioned before:
> >
> >
> > I noticed that you put new entries into struct symbol of type locexpr.
> > I'm not too sure if that is the correct to place them. In my
> > understanding these location expressions need only be associated with
> > the type of a symbol rather than the symbol itself.
> No, it describes the location of a symbol, not of a type.
> Two symbols of the same type could be in different places (one in
> register, one in memory).
> Think of location lists, too.
> I could have two symbols of the same type in completely different places
> in memory and registers, at a given time (IE each in two different live
> ranges).
Yes I agree for symbol location. However, other location expressions can
describe the lower and upper bounds of an array, or its stride,
associative and allocatable values. These are the ones that can be
located in the symbol's type. The main reason behind this, is that these
other locations are based off the location of the symbol.

> > This will remove
> > unnecessary replication of data and save the extra few bytes. Or am I
> > making to many assumptions here?
> Also, part of the idea of using our own bytecode was being able to
> describe the location of complex things, such a vtable entry, in a
> portable way.

Petr Sorfa                  Senior Software Engineer
430 Mountain Ave. 
Murray Hill 07974
Disclaimer: All my comments are my own and nobody else's

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]