Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Andrew Cagney <ac131313@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Type cleanups
Date: Mon, 13 May 2002 18:37:00 -0000	[thread overview]
Message-ID: <15584.27159.909100.892316@localhost.redhat.com> (raw)
In-Reply-To: <20020513230853.GA20143@nevyn.them.org>


Ok, I killed sh-hms, and in case you need it for this patch (I guess
Andrew already green-lighted it, though) you have my approval.

Elena


Daniel Jacobowitz writes:

 > On Mon, May 13, 2002 at 06:15:02PM -0400, Andrew Cagney wrote:
 > > >I don't get that on the three systems I use.  Bug in the system library?
 > > >
 > > >>
 > > >>Hmm, I'm not sure where the necessary preprocessor definitions are
 > > >>coming from to make that definition visible.  I'll look in to it.
 > > >
 > > >
 > > >Answer:  apparently it is standards-conforming to define JB_* in
 > > ><setjmp.h>.  This means that all of the tm-*.h files which define JB_
 > > >variables are somewhat dubious.  We should probably rename our copies
 > > >of these constants.  And kill the ones we don't use, which amounts to
 > > >almost all of them.
 > > 
 > > So something like:
 > > 
 > > /^#[[:space:]]*define[[:space:]]*JB_/
 > > 
 > > should be ARIed as well?
 > > 
 > > If yes, I'll do that and add a corresponding bug report.
 > 
 > That sounds like a good idea to me.  These constants obviously appear
 > in host headers, so we shouldn't be defining them for target headers.
 > The references will change name naturally when the definitions do.
 > 
 > -- 
 > Daniel Jacobowitz                           Carnegie Mellon University
 > MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-05-14  1:37 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-12 17:34 Daniel Jacobowitz
2002-05-12 20:18 ` Andrew Cagney
2002-05-12 20:40   ` Daniel Jacobowitz
2002-05-12 21:31     ` Andrew Cagney
2002-05-13 11:46       ` Daniel Jacobowitz
2002-05-13 12:54         ` Daniel Berlin
2002-05-13 12:57           ` Daniel Jacobowitz
2002-05-13  6:59   ` Daniel Jacobowitz
2002-05-13  8:37     ` Andrew Cagney
2002-05-13  8:51       ` Elena Zannoni
2002-05-13  9:11         ` Andrew Cagney
2002-05-13  9:19           ` Elena Zannoni
2002-05-13 11:50       ` Daniel Jacobowitz
2002-05-13 11:59         ` Daniel Jacobowitz
2002-05-13 15:14           ` Andrew Cagney
2002-05-13 16:09             ` Daniel Jacobowitz
2002-05-13 18:37               ` Elena Zannoni [this message]
2002-05-14 17:09               ` Andrew Cagney
2002-05-17  1:11     ` Eli Zaretskii
2002-05-17  8:02       ` Daniel Jacobowitz
2002-05-17  9:14         ` Eli Zaretskii
2002-05-17 10:21           ` Daniel Jacobowitz
2002-05-17 10:34             ` Andrew Cagney
2002-05-18  0:15               ` Eli Zaretskii
2002-05-18  0:13             ` Eli Zaretskii

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=15584.27159.909100.892316@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=ac131313@cygnus.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.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