public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@zembu.com>
To: mark@codesourcery.com
Cc: rth@cygnus.com, binutils@sourceware.cygnus.com
Subject: Re: Patches for IRIX6 N32-ABI ld
Date: Thu, 01 Jul 1999 00:00:00 -0000	[thread overview]
Message-ID: <19990626204616.9890.qmail@daffy.airs.com> (raw)
In-Reply-To: <19990626134622L.mitchell@codesourcery.com>

   From: Mark Mitchell <mark@codesourcery.com>
   Date: Sat, 26 Jun 1999 13:46:22 -0700

       Ian> In other words, I think either SGI_COMPAT should continue to
       Ian> be defined as a clearly boolean value (e.g., 1) or you should
       Ian> modify all the tests of SGI_COMPAT to work in some different
       Ian> manner.

   I understand what you're saying.  But, this is a common programming
   idiom, and well understood.  How about explicitly setting `sct_none'
   to zero:

     enum {
       sct_none = 0,
       ...
     }

   together with a comment?

I'm not sure why you want to bother, probably because I haven't seen
the rest of your patches.

Why not have two macros, one for general SGI compatibility, namely the
existing SGI_COMPAT, and one new one you can use to check just which
sort of SGI compatibility you want for a particular BFD?

Ian

  reply	other threads:[~1999-07-01  0:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-01  0:00 Mark Mitchell
1999-07-01  0:00 ` Richard Henderson
1999-07-01  0:00   ` Mark Mitchell
1999-07-01  0:00     ` Ian Lance Taylor
1999-07-01  0:00       ` Mark Mitchell
1999-07-01  0:00         ` Ian Lance Taylor [this message]
1999-07-01  0:00           ` Mark Mitchell
1999-07-01  0:00             ` Ian Lance Taylor
1999-07-01  0:00               ` Mark Mitchell
1999-07-01  0:00             ` Richard Henderson
1999-07-01  0:00               ` Mark Mitchell

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=19990626204616.9890.qmail@daffy.airs.com \
    --to=ian@zembu.com \
    --cc=binutils@sourceware.cygnus.com \
    --cc=mark@codesourcery.com \
    --cc=rth@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).