public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: Bruce Korb <bruce.korb@gmail.com>, libffi-discuss@sourceware.org
Subject: Re: pass by value and also snprintf()
Date: Mon, 27 Apr 2015 17:09:00 -0000	[thread overview]
Message-ID: <553E6D2E.7060403@redhat.com> (raw)
In-Reply-To: <CAKRnqNK1D9Wp3uedW62uVk-5FCfzGgDd0xOA2W9qMQeizV1TSw@mail.gmail.com>

On 04/27/2015 09:59 AM, Bruce Korb wrote:
> I hope
> there is an
> obvious answer to what I am missing:

Certainly there's no way we can help you further without a complete test case.


r~

  reply	other threads:[~2015-04-27 17:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-27 16:59 Bruce Korb
2015-04-27 17:09 ` Richard Henderson [this message]
2015-04-27 17:37   ` Bruce Korb
2015-04-27 17:45     ` Bruce Korb
2015-04-27 17:48       ` Bruce Korb
2015-04-27 18:02     ` Richard Henderson
2015-04-27 18:54       ` Bruce Korb

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=553E6D2E.7060403@redhat.com \
    --to=rth@redhat.com \
    --cc=bruce.korb@gmail.com \
    --cc=libffi-discuss@sourceware.org \
    /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).