From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: mec.gnu@mindspring.com, zack@codesourcery.com
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 21:36:00 -0000 [thread overview]
Message-ID: <20040405213626.694CA4B104@berman.michael-chastain.com> (raw)
Zack Weinberg writes:
> Not emitting them was unintentional, and I imagine getting them back
> would be straightforward. ... 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.
Cool. I've got a bug report all set to file, except that it looks
like the httpd on gcc.gnu.org just crashed! :-( You'll have it soon.
The bug does not happen with gcc gcc-3_4-branch so I agree it is
lesser priority than any 3.4 activity.
BTW, dwarf-2 is okay. I saw no regressions with gdb 6.0,
gdb test suite 6.0, gcc HEAD, and dwarf-2.
Michael C
next reply other threads:[~2004-04-05 21:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 21:36 Michael Elizabeth Chastain [this message]
2004-04-05 23:26 ` Zack Weinberg
-- strict thread matches above, loose matches on Subject: below --
2004-04-05 20:26 Michael Elizabeth Chastain
2004-04-05 20:47 ` 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=20040405213626.694CA4B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=drow@false.org \
--cc=ezannoni@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=zack@codesourcery.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