From: Zack Weinberg <zack@codesourcery.com>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: drow@false.org, ezannoni@redhat.com, gdb@sources.redhat.com,
jimb@redhat.com
Subject: Re: gcc HEAD, stabs+, TYPE_CODE_INT problem
Date: Mon, 05 Apr 2004 20:47:00 -0000 [thread overview]
Message-ID: <87lllai23a.fsf@egil.codesourcery.com> (raw)
In-Reply-To: <20040405202649.104DB4B104@berman.michael-chastain.com> (Michael Elizabeth Chastain's message of "Mon, 5 Apr 2004 16:26:49 -0400 (EDT)")
mec.gnu@mindspring.com (Michael Elizabeth Chastain) writes:
[...]
> gcc 3.3.3 (and gcc HEAD 20040323) emitted about 20 stab lines for the
> list from first_builtin_decl to last_builtin_decl. This provides gdb
> with names for "char", "int", "float", et cetera. gcc HEAD 20040330 no
> longer uses provides this list so there are no more stab lines for the
> builtin types. Can we change gcc to bring these builtins back?
Not emitting them was unintentional, and I imagine getting them back
would be straightforward. However, I don't know a lot about dbxout.c
and right now I have things to do for the 3.4.0 release (which doesn't
include these patches) that take priority - so I'm not likely to try
to fix this this week.
Would you please file a bug report against GCC, and assign it to me?
And any further investigation you could do would be greatly appreciated.
zw
next prev parent reply other threads:[~2004-04-05 20:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 20:26 Michael Elizabeth Chastain
2004-04-05 20:47 ` Zack Weinberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-05 21:36 Michael Elizabeth Chastain
2004-04-05 23:26 ` Zack Weinberg
2004-04-05 19:09 Michael Elizabeth Chastain
2004-04-05 19:32 ` Daniel Jacobowitz
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=87lllai23a.fsf@egil.codesourcery.com \
--to=zack@codesourcery.com \
--cc=drow@false.org \
--cc=ezannoni@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@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