public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/13795] New: .gdb_index misses fortran calling convention setting?
Date: Fri, 02 Mar 2012 17:02:00 -0000	[thread overview]
Message-ID: <bug-13795-4717@http.sourceware.org/bugzilla/> (raw)

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

             Bug #: 13795
           Summary: .gdb_index misses fortran calling convention setting?
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: minor
          Priority: P2
         Component: symtab
        AssignedTo: unassigned@sourceware.org
        ReportedBy: dje@google.com
    Classification: Unclassified


Found this while reading the code.
Filing it so it's not forgotten.

read_partial_die has this:

        case DW_AT_calling_convention:
          /* DWARF doesn't provide a way to identify a program's source-level   
             entry point.  DW_AT_calling_convention attributes are only meant   
             to describe functions' calling conventions.                        

             However, because it's a necessary piece of information in          
             Fortran, and because DW_CC_program is the only piece of debugging  
             information whose definition refers to a 'main program' at all,    
             several compilers have begun marking Fortran main programs with    
             DW_CC_program --- even when those functions use the standard       
             calling conventions.                                               

             So until DWARF specifies a way to provide this information and     
             compilers pick up the new representation, we'll support this       
             practice.  */
          if (DW_UNSND (&attr) == DW_CC_program
              && cu->language == language_fortran)
            {
              set_main_name (part_die->name);

              /* As this DIE has a static linkage the name would be difficult   
                 to look up later.  */
              language_of_main = language_fortran;
            }
          break;

I couldn't see the corresponding support in .gdb_index handling.

-- 
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.


             reply	other threads:[~2012-03-02 17:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-02 17:02 dje at google dot com [this message]
2021-02-23 18:57 ` [Bug symtab/13795] .gdb_index misses main name tromey at sourceware dot org
2021-02-23 18:57 ` tromey at sourceware dot org
2021-03-28 16:00 ` tromey at sourceware dot org
2023-12-10 15:27 ` tromey at sourceware dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-13795-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).