From: Mark Kettenis <kettenis@chello.nl>
To: mec@shout.net
Cc: brobecker@gnat.com, gdb@sources.redhat.com
Subject: Re: 8-byte register values on a 32-bit machine
Date: Sat, 01 Mar 2003 22:46:00 -0000 [thread overview]
Message-ID: <200303012246.h21MkTc2035390@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <200303012057.h21KvFv26400@duracef.shout.net> (message from Michael Elizabeth Chastain on Sat, 1 Mar 2003 14:57:15 -0600)
Date: Sat, 1 Mar 2003 14:57:15 -0600
From: Michael Elizabeth Chastain <mec@shout.net>
The heinous part is that gdb *knows* it is pulling some register
value out of its ass for p1.y. I understand that on some targets,
gcc and gdb might agree on register number allocation (ignore for
the moment that there are other compilers besides gcc). Okay, for
targets where we have a guarantee about that, then enable
sequential register access. But i686-pc-linux-gnu is definitely
not such a target.
I don't agree with the defenitely here. GCC has been allocating the
registers in a well determined order for at least 10 years now.
Mark
next prev parent reply other threads:[~2003-03-01 22:46 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-01 20:57 Michael Elizabeth Chastain
2003-03-01 22:46 ` Mark Kettenis [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-14 16:27 Michael Elizabeth Chastain
2003-03-13 4:18 Michael Elizabeth Chastain
2003-03-13 17:05 ` Andrew Cagney
2003-03-12 19:09 Michael Elizabeth Chastain
2003-03-12 20:47 ` Andrew Cagney
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-02 6:52 Michael Elizabeth Chastain
2003-03-02 9:35 ` Stephane Carrez
2003-03-03 4:50 ` Daniel Jacobowitz
2003-02-24 2:36 Michael Elizabeth Chastain
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
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=200303012246.h21MkTc2035390@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=brobecker@gnat.com \
--cc=gdb@sources.redhat.com \
--cc=mec@shout.net \
/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).