On Tue, 5 Dec 2006, Markus Franke wrote:
> I want to port an existing backend (based on version gcc-2.7.2.3) on the
> most recent release (gcc-4.1.1). During compilation process I get
> several messages about some poisened macro definitions. The macros which
> make problems are liste
From: Markus Franke <[EMAIL PROTECTED]>
To: gcc@gcc.gnu.org
Date: Tue, 05 Dec 2006 21:37:30 +0100
Subject: poisened macro definitions
Dear GCC Developers,
I want to port an existing backend (based on version gcc-2.7.2.3) on the
most recent release (gcc-4.1.1). During compilation process
I read something about poisened macros and that they shouldn't be used
anymore. But in fact I was not able to find any documentation about
these macros. When were they declared as poisened and especially why?
What should be done instead of using this macros? Just uncommenting
everything can't be
Dear GCC Developers,
I want to port an existing backend (based on version gcc-2.7.2.3) on the
most recent release (gcc-4.1.1). During compilation process I get
several messages about some poisened macro definitions. The macros which
make problems are listed below:
---snip
