From: "Zack Weinberg" <zack@codesourcery.com>
To: Ken Faiczak <kfaiczak@sandvine.com>
Cc: 'David Edelsohn' <dje@watson.ibm.com>, "'gcc@gnu.org'" <gcc@gnu.org>
Subject: Re: incorrect __vxworks__ usage in longlong.h (3.3) was ok in 3.2 .3
Date: Wed, 30 Jul 2003 19:58:00 -0000 [thread overview]
Message-ID: <87el073k2t.fsf@egil.codesourcery.com> (raw)
In-Reply-To: <FE045D4D9F7AED4CBFF1B3B813C853370285726E@mail.sandvine.com> (Ken Faiczak's message of "Wed, 30 Jul 2003 14:55:30 -0400")
Ken Faiczak <kfaiczak@sandvine.com> writes:
> Note: also the check of PPC also causes problems for vxworks
> since it also defines that as a CPU_FAMILY for comparison
> even though the current CPU is not equal to that
> (it also defines all kinds of others CPUs and FAMILIES...)
>
> ie in our case CPU=R4000 or CPU=SB1250
>
> is the compiler supposed to be looking for these sorts of things
> that aren't surrounded by __PPC__ sort of thing
It's suboptimal, but please understand that this file is lifted from
GMP, and changes really ought to go through the GMP maintainers.
I don't care to defend vxworks' pollution of the user namespace with
CPU and CPU_FAMILY macros, either.
zw
prev parent reply other threads:[~2003-07-30 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 19:54 Ken Faiczak
2003-07-30 19:58 ` Zack Weinberg [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=87el073k2t.fsf@egil.codesourcery.com \
--to=zack@codesourcery.com \
--cc=dje@watson.ibm.com \
--cc=gcc@gnu.org \
--cc=kfaiczak@sandvine.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).