From: Roland McGrath <roland@redhat.com>
To: Richard Henderson <rth@twiddle.net>
Cc: libc-hacker@sources.redhat.com
Subject: Re: FR-V PLT audit
Date: Thu, 10 Feb 2005 07:19:00 -0000 [thread overview]
Message-ID: <200502100719.j1A7JQRn009078@magilla.sf.frob.com> (raw)
In-Reply-To: Richard Henderson's message of Wednesday, 9 February 2005 23:06:48 -0800 <20050210070648.GA4296@twiddle.net>
> On Wed, Feb 09, 2005 at 10:43:48PM -0800, Roland McGrath wrote:
> > Indeed, what is the motivation for using an anonymous union rather than
> > each sysdeps/CPU/ldsodefs.h defining a macro for the appropriate thing?
>
> Or any macros at all? What's so special about the argument and result
> registers that require structure names to differ by target? We don't
> do that for sigcontext, or jmp_buf.
I think the intent there was just that the structure member names match the
names of the entry point symbols in the audit library. The reason the API
for those functions uses a different name for each CPU is that the
signature and what you need to know to implement it also differ for each
CPU. It is not something that is ever used generically like sigcontext and
jmp_buf are.
next prev parent reply other threads:[~2005-02-10 7:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ork6ppa9ev.fsf@livre.redhat.lsd.ic.unicamp.br>
2005-02-07 9:15 ` Fujitsu FR-V port (linuxthreads and nptl included) Alexandre Oliva
2005-02-07 19:37 ` Roland McGrath
2005-02-09 9:38 ` elf.h changes for FR-V FDPIC and TLS Alexandre Oliva
2005-03-13 9:17 ` Roland McGrath
2005-02-09 9:48 ` Fujitsu FR-V port (linuxthreads and nptl included) Alexandre Oliva
2005-02-09 9:57 ` Ulrich Drepper
2005-02-09 11:30 ` Alexandre Oliva
2005-03-13 9:15 ` Roland McGrath
2005-02-09 9:57 ` Introduce TRY_STATIC_TLS macro, used in FR-V Alexandre Oliva
2005-02-09 10:10 ` Ulrich Drepper
2005-02-09 11:07 ` Alexandre Oliva
2005-02-09 10:08 ` FR-V TLS macros Alexandre Oliva
2005-02-09 10:13 ` Ulrich Drepper
2005-02-09 11:15 ` Alexandre Oliva
2005-03-13 9:09 ` Roland McGrath
2005-02-09 11:01 ` FR-V PLT audit Alexandre Oliva
2005-02-09 11:15 ` Ulrich Drepper
2005-02-10 5:16 ` Richard Henderson
2005-02-10 6:43 ` Roland McGrath
2005-02-10 7:06 ` Richard Henderson
2005-02-10 7:19 ` Roland McGrath [this message]
2005-02-10 7:51 ` Richard Henderson
2005-02-10 9:03 ` Roland McGrath
2005-02-10 16:51 ` Richard Henderson
2005-02-09 11:02 ` using pre-TCB padding for static TLS Alexandre Oliva
2005-02-09 11:14 ` Ulrich Drepper
2005-02-09 11:35 ` Alexandre Oliva
2005-02-09 11:02 ` FR-V set_tid_address syscall number Alexandre Oliva
2005-02-09 11:11 ` Ulrich Drepper
2005-02-09 11:36 ` Alexandre Oliva
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=200502100719.j1A7JQRn009078@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=rth@twiddle.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).