From: Joel Brobecker <brobecker@adacore.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: PING: [RFA/i386] 2 more patterns in i386_analyze_stack_align
Date: Sun, 31 Dec 2006 14:39:00 -0000 [thread overview]
Message-ID: <20061231143903.GB3428@adacore.com> (raw)
In-Reply-To: <200612311215.kBVCF75Z010607@brahms.sibelius.xs4all.nl>
> Hmm, you're missing the %ebx case here. Now on ELF systems, you'll
> probably never see it since %ebx is used for GOT access, but on other
> object formats I don't think there is any reason why GCC wouldn't
> choose to use %ebx as well.
I can easily add the %ebx case as well, but I don't think GCC would
currently use that register in any configuration. I'll double-check
with one of my coworkers who told me about the other alternatives to
using %ecx, but it will have to wait for a few days until the holidays
are over. He told me about this after having looked at the code in GCC,
so I would be surprised if he did not see the %ebx case... Note that
even if GCC did not currently use %ebx, I don't mind adding support
for it, JIC.
> This looks reasonable otherwise, except that I would sort the patterns
> in a more logical order.
I sorted them in the order that GCC would use them. I don't mind sorting
them in a different order, if you like.
I will take this as approval, and wait for your comments to see if
you'd like me to submit followup patches: adding support for the use
of the %ebx case, and altering the patterns order.
Thanks Mark,
--
Joel
next prev parent reply other threads:[~2006-12-31 14:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 10:49 Joel Brobecker
2006-12-31 6:08 ` PING: " Joel Brobecker
2006-12-31 12:15 ` Mark Kettenis
2006-12-31 14:39 ` Joel Brobecker [this message]
2007-01-05 6:48 ` Joel Brobecker
2007-01-05 11:05 ` Mark Kettenis
2007-01-05 14:36 ` Joel Brobecker
2007-01-05 14:58 ` Mark Kettenis
2007-01-05 16:42 ` Joel Brobecker
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=20061231143903.GB3428@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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