From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com, gdb@sources.redhat.com
Subject: 8-byte register values on a 32-bit machine
Date: Mon, 24 Feb 2003 02:36:00 -0000 [thread overview]
Message-ID: <200302240235.h1O2Zws05373@duracef.shout.net> (raw)
I saw a regression in gdb.base/store.exp this week:
gdb.base/store.exp: new check struct 4
PASS -> FAIL
This happens with gcc 2.95.3 -gdwarf-2.
This happens because gcc 2.95.3 puts an 8-byte variable into a pair of
4-byte registers. (gcc 3.2.2 puts the variable into memory so the
problem never arises -- but I bet it will come back for things like
FORTRAN complex numbers, which are very natural for register pairs).
It happened this particular week because the old dwarf-2 code had some
code to handle multi-register variables, although the code doesn't
appear to work for me. The new dwarf-2 code just completely spaces
in the case of multi-register variables.
We need to figure out what the right symbol table information is for
multi-register variables. If gcc is emitting good symbol table
information, gdb can do its job, and I can write a test case for it.
But I suspect that gcc 2.95.3 tells us about just one register and that
we can't win. But gdb can at least say "hmmm, you are trying to print 8
bytes from reg0, I can't do that", rather than print 4 bytes of correct
information and 4 bytes of rat poison. I think that would be acceptable
support for 2.95.3.
I filed a PR and I'll attach some executables to it.
Michael C
next reply other threads:[~2003-02-24 2:36 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 2:36 Michael Elizabeth Chastain [this message]
2003-03-01 13:35 ` Mark Kettenis
2003-03-01 20:33 ` Joel Brobecker
2003-03-01 22:38 ` Mark Kettenis
2003-03-01 23:41 ` Andrew Cagney
2003-03-02 0:28 ` Daniel Jacobowitz
2003-03-03 11:26 ` Richard Earnshaw
2003-03-03 11:52 ` Keith Walker
2003-03-01 23:39 ` Andrew Cagney
2003-03-01 20:57 Michael Elizabeth Chastain
2003-03-01 22:46 ` Mark Kettenis
2003-03-02 6:52 Michael Elizabeth Chastain
2003-03-02 9:35 ` Stephane Carrez
2003-03-03 4:50 ` Daniel Jacobowitz
2003-03-02 16:59 Michael Elizabeth Chastain
2003-03-12 15:35 ` Andrew Cagney
2003-03-12 15:51 ` Daniel Jacobowitz
2003-03-12 16:57 ` Andrew Cagney
2003-03-12 17:01 ` Daniel Jacobowitz
2003-03-12 18:15 ` Andrew Cagney
2003-03-12 18:29 ` Andrew Cagney
2003-03-12 18:35 ` Daniel Jacobowitz
2003-03-12 18:38 ` Andrew Cagney
2003-03-12 18:48 ` Paul Koning
2003-03-12 19:00 ` Daniel Jacobowitz
2003-03-12 21:04 ` Andrew Cagney
2003-03-12 20:06 ` Daniel Jacobowitz
2003-03-12 19:09 Michael Elizabeth Chastain
2003-03-12 20:47 ` Andrew Cagney
2003-03-13 4:18 Michael Elizabeth Chastain
2003-03-13 17:05 ` Andrew Cagney
2003-03-14 16:27 Michael Elizabeth Chastain
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=200302240235.h1O2Zws05373@duracef.shout.net \
--to=mec@shout.net \
--cc=drow@mvista.com \
--cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).