From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Paul Koning <pkoning@equallogic.com>,
mec@shout.net, stcarrez@nerim.fr, brobecker@gnat.com,
gdb@sources.redhat.com, kettenis@chello.nl
Subject: Re: 8-byte register values on a 32-bit machine
Date: Wed, 12 Mar 2003 20:06:00 -0000 [thread overview]
Message-ID: <20030312194533.GA8630@nevyn.them.org> (raw)
In-Reply-To: <3E6F8D38.6030207@redhat.com>
On Wed, Mar 12, 2003 at 02:40:40PM -0500, Andrew Cagney wrote:
> >
> >I don't know if it would break or not.
> >
> >
> >>If that's not the current proposal, could you reword it to help
> >>eliminate the confusion over what you intend?
> >
> >
> >No one is proposing to leave it broken. To pull up an example from
> >earlier in the thread, Andrew broke x86-64 when working on the frame
> >changes. It was an accident, and eventually fixed (by Michal Ludvig, I
> >might add). I apparently broke long long (in registers) in some of my
> >DWARF-2 support patches. I'm working to fix it. I'm only one person
> >and I only have so much time.
>
> For this `long long' case, can a simple local tweak that restores
> existing behavior (while the new code is finished / tested). That way
> the pressure is off you to get this stuff finished quickly instead of
> cleanly.
Except that I don't think such a local tweak is possible in this case.
I could be wrong. Anyone's welcome to try, including the maintainers
of the code in question.
I'm working on the proper solution. Hold your horses, people.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-03-12 20:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [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 6:52 Michael Elizabeth Chastain
2003-03-02 9:35 ` Stephane Carrez
2003-03-03 4:50 ` Daniel Jacobowitz
2003-03-01 20:57 Michael Elizabeth Chastain
2003-03-01 22:46 ` Mark Kettenis
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=20030312194533.GA8630@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=brobecker@gnat.com \
--cc=gdb@sources.redhat.com \
--cc=kettenis@chello.nl \
--cc=mec@shout.net \
--cc=pkoning@equallogic.com \
--cc=stcarrez@nerim.fr \
/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).