From: rbmj <rbmj@verizon.net>
To: gcc-help@gcc.gnu.org
Subject: Fixincludes machine_name fix overly zealous
Date: Tue, 29 May 2012 21:23:00 -0000 [thread overview]
Message-ID: <4FC53E40.3060708@verizon.net> (raw)
Hi all,
So, now that I got fixincludes to work with me, there is only one
barrier to getting everything working for me.
The machine_name fix seems to be overly zealous. It is replacing many
instances of
#if((n)def) ... CPU ...
with
#if((n)def) ... __CPU__
Which is ok, except for the fact that it does *not* replace CPU
everywhere else, including in #el* clauses *and* outside of the
preprocessor, where use of CPU is reported as an error.
It is also replacing __CPU_FAMILY__, which is also undesirable.
Why is it replacing these? AFAIK they do not need to be replaced and
should not be replaced.
Other than this issue, everything else appears to be working well.
Thanks for any/all help!
Robert Mason
reply other threads:[~2012-05-29 21:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4FC53E40.3060708@verizon.net \
--to=rbmj@verizon.net \
--cc=gcc-help@gcc.gnu.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 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).