From: Andrew Cagney <cagney@gnu.org>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Signal Trampoline Frames
Date: Thu, 25 Mar 2004 00:26:00 -0000 [thread overview]
Message-ID: <40622721.6010603@gnu.org> (raw)
In-Reply-To: <200403242303.i2ON33uL005973@elgar.kettenis.dyndns.org>
> Andrew,
>
> It's probably too late now, but I have the feeling this new
> tramp-frame.c is not generic enough. It assumes fixed-length
> instructions (which makes it unsuitable for IA-32 and AMD64)
I didn't forget IA-32, I figured that it is always little endian so a
sequence of one byte "insns" would work.
> and uses
> the arbitrary number 8 for the number of instructions (which makes it
> not quite suitable for SPARC).
I'm assuming people will increase it (It's like the arbitrary number 16
for the largest possible size of an instruction).
> The whole thing seems a bit
> over-engineered to me :-(.
In what way?
I wrote it after churn out 4 almost identical signal trampolines - so it
works for one type but not for others. You also haven't seen my test
cases :-)
> Anyway, you might want to conseider the attached patch, which makes
> the comments catch up with reality. The extra whitespace is there to
> guide the eye and make the distinction between the instruction
> sequence members and the initialization function clear.
Andrew
next prev parent reply other threads:[~2004-03-25 0:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-24 23:03 Mark Kettenis
2004-03-25 0:26 ` Andrew Cagney [this message]
2004-03-25 10:26 ` Mark Kettenis
2004-03-25 14:42 ` 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=40622721.6010603@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.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