Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: ezannoni@redhat.com, gdb@sources.redhat.com
Subject: Re: FORTRAN_HACK macro?
Date: Fri, 09 Jan 2004 15:30:00 -0000	[thread overview]
Message-ID: <16382.51392.626691.65583@localhost.redhat.com> (raw)
In-Reply-To: <20040108232505.E9A384B35A@berman.michael-chastain.com>

Michael Elizabeth Chastain writes:
 > Beats me.  Here's some fact-crumbs:
 > 
 >   dwarf2read.c was not in gdb 4.16.
 >   dwarf2read.c was in gdb 4.17, dated 1998-01-28
 >   1998-01-28 version already has FORTRAN_HACK
 >   code around FORTRAN_HACK is about the same as it is today
 >   ChangeLog-96 says dwarf2read.c introduced on 1996-07-19.
 > 
 > grepping on 'read_array_type' in the ChangeLogs turns up:
 > 
 >   1996-12-01:
 > 
 >     (dwarf_read_array_type):  Handle variable length arrays.
 >     Use lookup_pointer_type instead of handcrafting a type.
 >     Create array type only if a DW_TAG_subrange_type was found.
 > 
 >   1997-01-25:
 >     (read_array_type):  Renamed from dwarf_read_array_type.
 >     Default upper array bound to describe an array with unspecified
 >     length.
 >     Create array types in backwards order, as dwarf2 puts out the array
 >     dimensions from left to right.
 > 
 >   1998-01-28:
 > 
 >     (read_array_type): Fix langauge test.
 > 
 > If the FORTRAN_HACK was in the 1996-07-19 version then I would guess
 > that it is an unimplemented stub and can be killed/replaced easily.

yes I think it was there since the first incarnation of the file. It
hasn't been touched except for that one in 96. 

 > 
 > If it was added after 1996-07-19 then someone was trying to do
 > something.
 > 

I don't think it was.

elena

 > Michael C


  reply	other threads:[~2004-01-09 15:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-08 23:25 Michael Elizabeth Chastain
2004-01-09 15:30 ` Elena Zannoni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-08 22:32 Elena Zannoni
2004-01-08 23:24 ` Jim Blandy
2004-01-09 15:26   ` Elena Zannoni
2004-01-10  2:18 ` Richard Henderson
2004-01-13 21:22 ` Stan Shebs

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=16382.51392.626691.65583@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=mec.gnu@mindspring.com \
    /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