[Bug symtab/13035] New: -gdwarf-2 struct fields have wrong offset

[Bug symtab/13035] New: -gdwarf-2 struct fields have wrong offset

[jan.kratochvil at redhat dot com]

http://sourceware.org/bugzilla/show_bug.cgi?id=13035

           Summary: -gdwarf-2 struct fields have wrong offset
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: symtab
        AssignedTo: unassigned@sourceware.org
        ReportedBy: jan.kratochvil@redhat.com
            Target: x86_64-fedora16-linux-gnu


Created attachment 5865
  --> http://sourceware.org/bugzilla/attachment.cgi?id=5865
decode_locdesc reimplementation + testcase

GCC now requires full expression evaluatior instead of just decode_locdesc.
This is its implementation + testcase.
But it has regressions, it would need DWARF expression for
TYPE_BASECLASS_BITPOS but that infrastructure is only in
archer-jankratochvil-vla.
TYPE_BASECLASS_BITPOS works only by accident now seems to me.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug symtab/13035] -gdwarf-2 struct fields have wrong offset

[jan.kratochvil at redhat dot com]

http://sourceware.org/bugzilla/show_bug.cgi?id=13035

Jan Kratochvil <jan.kratochvil at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

--- Comment #1 from Jan Kratochvil <jan.kratochvil at redhat dot com> 2011-07-27 15:32:04 UTC ---
I will track it in the mailing list, this Bug has no real info:
[patch 2/2] Fix decode_locdesc for gcc-4.7.x optimized DWARF
http://sourceware.org/ml/gdb-patches/2011-07/msg00762.html

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.