Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: luisgpm@linux.vnet.ibm.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] printf support for DFP values
Date: Mon, 29 Oct 2007 20:12:00 -0000	[thread overview]
Message-ID: <ur6jdr8iy.fsf@gnu.org> (raw)
In-Reply-To: <1193669215.4800.10.camel@localhost> (message from Luis Machado 	on Mon, 29 Oct 2007 11:46:55 -0300)

> From: Luis Machado <luisgpm@linux.vnet.ibm.com>
> Cc: gdb-patches@sourceware.org
> Date: Mon, 29 Oct 2007 11:46:55 -0300
> 
> > > -	double_arg, long_double_arg
> > > +	double_arg, long_double_arg, decfloat_arg
> > 
> > You are using decfloat_arg unconditionally, but I don't see it defined
> > anywhere in today's CVS.  Am I missing something?
> 
> decfloat_arg is being defined in an "enum" structure together with the
> other values (double_arg, long_double_arg, int_arg etc).

Defined where?  I probably missed some file, because I searched for it
in the current CVS and couldn't find, and neither do I see it in your
patch.


  reply	other threads:[~2007-10-29 20:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-27  6:25 Luis Machado
2007-10-27 12:05 ` Eli Zaretskii
2007-10-29 15:03   ` Luis Machado
2007-10-29 20:12     ` Eli Zaretskii [this message]
2007-10-29 20:19       ` Daniel Jacobowitz
2007-10-30  4:20         ` Eli Zaretskii
2007-10-30  4:39           ` Eli Zaretskii
2007-10-30 18:19             ` Luis Machado
2007-10-30 20:58               ` Eli Zaretskii
2007-11-01  1:18                 ` Luis Machado
2007-11-01  4:11                   ` Eli Zaretskii
2007-11-01 10:21                     ` Andreas Schwab
2007-11-01 12:02                       ` Luis Machado
2007-11-02 12:05                         ` Eli Zaretskii
2007-11-01 15:34                   ` Daniel Jacobowitz
2007-11-01 16:00                     ` Luis Machado
2007-11-02 12:07                       ` Eli Zaretskii
2007-11-05 11:35                         ` Luis Machado

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=ur6jdr8iy.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=luisgpm@linux.vnet.ibm.com \
    /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