From: Pedro Alves <palves@redhat.com>
To: "Maciej W. Rozycki" <macro@imgtec.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Restore the order of file lists in features/Makefile
Date: Tue, 08 Nov 2016 14:48:00 -0000 [thread overview]
Message-ID: <794ebe50-9058-1df7-24d6-25c0e8fdb8ec@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1610281513350.31859@tp.orcam.me.uk>
On 10/28/2016 03:52 PM, Maciej W. Rozycki wrote:
> # Record which registers should be sent to GDB by default after stop.
> aarch64-expedite = x29,sp,pc
> +amd64-expedite = rbp,rsp,rip
> arm-expedite = r11,sp,pc
> i386-expedite = ebp,esp,eip
> -amd64-expedite = rbp,rsp,rip
> -x32-expedite = rbp,rsp,rip
> -mips-expedite = r29,pc
...
> +tic6x-c64x-linux-expedite = A15,PC
> +tic6x-c64xp-expedite = A15,PC
> +tic6x-c64xp-linux-expedite = A15,PC
> +x32-expedite = rbp,rsp,rip
>
It's a bit of a shame that amd64, i386 and x32 get split up.
And they'll get further and further away as we add more entries.
How bad would it look if we said it's "mostly" sorted? E.g.,
# Record which registers should be sent to GDB by default after
# stop. Mostly alpha-sorted, except when it makes sense to group
# architectures.
amd64-expedite = rbp,rsp,rip
i386-expedite = ebp,esp,eip
x32-expedite = rbp,rsp,rip
aarch64-expedite = x29,sp,pc
arm-expedite = r11,sp,pc
...
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-11-08 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 14:53 Maciej W. Rozycki
2016-11-08 8:49 ` [PING][PATCH] " Maciej W. Rozycki
2016-11-08 13:23 ` Simon Marchi
2016-11-08 14:37 ` [PATCH] " Yao Qi
2016-11-08 14:48 ` Pedro Alves [this message]
2016-11-08 14:55 ` Pedro Alves
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=794ebe50-9058-1df7-24d6-25c0e8fdb8ec@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=macro@imgtec.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