From: Fred Fish <fnf@public.ninemoons.com>
To: jimb@redhat.com (Jim Blandy)
Cc: fnf@ninemoons.com, gcc-bugs@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: [RFC] Possible gcc/DWARF or gdb/DWARF problem
Date: Mon, 01 Dec 2003 16:42:00 -0000 [thread overview]
Message-ID: <200312011641.hB1GfllT010281@fred.ninemoons.com> (raw)
In-Reply-To: <vt28ylw5zuh.fsf@zenia.home> from "Jim Blandy" at Dec 01, 2003 10:20:38 AM
> it uses 32-bit stores and loads to fb+0 to access
> it, but that's irrelevant; it's a one-byte value.) Right?
Correct.
> You're right --- GCC is wrong.
I'll go ahead and file a formal gcc bug report.
-Fred
prev parent reply other threads:[~2003-12-01 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-29 20:26 Fred Fish
2003-12-01 1:54 ` Daniel Jacobowitz
2003-12-01 15:21 ` Jim Blandy
2003-12-01 16:42 ` Fred Fish [this message]
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=200312011641.hB1GfllT010281@fred.ninemoons.com \
--to=fnf@public.ninemoons.com \
--cc=fnf@ninemoons.com \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=jimb@redhat.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