All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Momchil 'Velco' Velikov" <velco@fadata.bg>
To: Bob Toxen <bob@roger.realminfo.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Nested stdarg broken?
Date: Wed, 27 Oct 1999 09:08:09 +0300	[thread overview]
Message-ID: <381696C9.43512555@fadata.bg> (raw)
In-Reply-To: 199910262303.TAA26743@roger.realminfo.com


Bob Toxen wrote:
> 
> My application uses stdarg (#include <stdarg.h>, va_start, and friends)
> in a function that then calls vfprintf which also uses stdarg.
> 
> The variable args get garbled by the time they get to vfprintf.  The
> fmt arg does not get garbled.
Here's what you can read at
http://egcs.cygnus.com/gcc-2.95/gcc-2.95.1.html
under section "Platform specific bugfixes and improvements"
         Fix varargs/stdarg code generation bug for rs6000/ppc svr4
targets. 
Maybe this helps, maybe not.

Regards,
-velco

btw, 2.95.2 is out

-velco

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      reply	other threads:[~1999-10-27  6:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-26 23:03 Nested stdarg broken? Bob Toxen
1999-10-27  6:08 ` Momchil 'Velco' Velikov [this message]

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=381696C9.43512555@fadata.bg \
    --to=velco@fadata.bg \
    --cc=bob@roger.realminfo.com \
    --cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.