From: Ian Lance Taylor <iant@google.com>
To: "Sivaprasad.pv" <sivaprasad.pv@redpinesignals.com>
Cc: gcc <gcc-help@gcc.gnu.org>
Subject: Re: Migrating from gcc-3.3 to gcc-4.2
Date: Thu, 14 Aug 2008 06:38:00 -0000 [thread overview]
Message-ID: <m3iqu4i3pl.fsf@google.com> (raw)
In-Reply-To: <48A3B053.1080208@redpinesignals.com> (Sivaprasad pv's message of "Thu\, 14 Aug 2008 09\:40\:59 +0530")
"Sivaprasad.pv" <sivaprasad.pv@redpinesignals.com> writes:
> I want to upgrade our gcc cross compiler from gcc-3.3 to gcc-4.2.
> I have made direct attempt but I got following error messages .
>
> error: attempt to use poisoned "TARGET_SWITCHES"
> error: attempt to use poisoned "DEFAULT_SHORT_ENUMS"
> error: attempt to use poisoned "SMALL_STACK"
> error: attempt to use poisoned "FUNCTION_ARG_PASS_BY_REFERENCE"
> error: attempt to use poisoned "MUST_PASS_IN_STACK"
> error: attempt to use poisoned "FUNCTION_ARG_PARTIAL_NREGS"
> error: attempt to use poisoned "EXPAND_BUILTIN_VA_ARG"
> error: attempt to use poisoned "TARGET_MEM_FUNCTIONS"
> error: attempt to use poisoned "CONST_COSTS"
> error: attempt to use poisoned "RTX_COSTS"
> error: attempt to use poisoned "ADDRESS_COST"
> error: attempt to use poisoned "PROMOTE_PROTOTYPES"
> error: attempt to use poisoned "INIT_TARGET_OPTABS"
>
> I think all these macro's are deprecated in gcc-4.2.
> Can any body suggest me how to find an equivalent macro's in gcc.4.2.
> Is there any specific documents available to upgrade from gcc-3.3 to
> gcc-4.2 ?
There is no specific document. Read the gcc 4.2 internals manual.
Most of the ones you mention have changed from target macros to target
hooks.
Ian
prev parent reply other threads:[~2008-08-14 5:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 5:09 Sivaprasad.pv
2008-08-14 6:38 ` Ian Lance Taylor [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=m3iqu4i3pl.fsf@google.com \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=sivaprasad.pv@redpinesignals.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).