Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@codesourcery.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: bauerman@br.ibm.com,  gdb-patches@sourceware.org
Subject: Re: [RFA] Fix float argument passing in inferior function calls for 	ppc64
Date: Tue, 15 Jan 2008 17:23:00 -0000	[thread overview]
Message-ID: <m3hchfoven.fsf@codesourcery.com> (raw)
In-Reply-To: <200801151443.m0FEhxN3021953@brahms.sibelius.xs4all.nl> (Mark Kettenis's message of "Tue, 15 Jan 2008 15:43:59 +0100 (CET)")


Have you folks ever seen this paper?

    http://www.eecs.harvard.edu/~nr/pubs/staged-abstract.html

    We present staged allocation, a technique for specifying calling
    conventions by composing tiny allocators called stages. A
    specification written using staged allocation has a precise, formal
    semantics, and it can be executed directly inside a
    compiler. Specifications of nine standard C calling conventions range
    in size from 15 to 30 lines each. An implementation of staged
    allocation takes about 250 lines of ML or 650 lines of C++. Each
    specification can be used not only to help a compiler implement the
    calling convention but also to generate a test suite.

It seems like an interpreter for this language would take very little
effort to implement in GDB, and could save quite a bit of effort.


  reply	other threads:[~2008-01-15 17:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-15 12:34 Thiago Jung Bauermann
2008-01-15 14:44 ` Mark Kettenis
2008-01-15 17:23   ` Jim Blandy [this message]
2008-01-15 17:40   ` Thiago Jung Bauermann
2008-01-15 20:34     ` Thiago Jung Bauermann
2008-01-15 20:48       ` Mark Kettenis
2008-01-15 20:55         ` Thiago Jung Bauermann
2008-01-16 12:49           ` Thiago Jung Bauermann
2008-01-16 14:45             ` Luis Machado
2008-01-25 15:58             ` Thiago Jung Bauermann
2008-01-25 16:06               ` Thiago Jung Bauermann
2008-01-31 22:12               ` Daniel Jacobowitz
2008-02-01 15:19                 ` Thiago Jung Bauermann

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=m3hchfoven.fsf@codesourcery.com \
    --to=jimb@codesourcery.com \
    --cc=bauerman@br.ibm.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