* Re: Macros being updated??
2003-05-27 9:15 Macros being updated?? Roger.Gough
@ 2003-05-27 9:15 ` Alexandre Courbot
0 siblings, 0 replies; 2+ messages in thread
From: Alexandre Courbot @ 2003-05-27 9:15 UTC (permalink / raw)
To: Roger.Gough, 'gcc@gcc.gnu.org'
> I am hoping somebody will be able to helpl me with this. I am trying to
> target a new architecure using gcc-3.2.2. I am trying to do this by
> modifying the target files which were written for gcc-2.95. I understand
> these target files and its architecture is similar to my own. I already had
> to modify some macros using the target hooks. (thanks Alex for that).
> Now however I get the following error with the file c-decl.c. I have an
> inkling that it has something to do with a target macro being modified
> since gcc -2.95. Anyway this is the error I get:
This looks like a syntax error in your macros. They get expanded in GCC code
and the error only happen when the expanded code is compiled. Have a look at
the positions GCC tells you there are errors at, and check your macros for
correctness. This is probably a dumb error, like forgetting a ";" at the end
of a declaration or something.
As for the differences between gcc 2.95 and 3.2, I guess if you redefine the
poisonned macros as hooks, fix things that don't compile because of obsolete
macros and add the new macros that are needed, you shouldn't have much
trouble. Can't help much, since I've started looking at GCC from 3.0.
Alex.
PS: please don't CC individuals directly when starting a new topic - people
who are able to reply you will do it anyway! ;)
^ permalink raw reply [flat|nested] 2+ messages in thread
* Macros being updated??
@ 2003-05-27 9:15 Roger.Gough
2003-05-27 9:15 ` Alexandre Courbot
0 siblings, 1 reply; 2+ messages in thread
From: Roger.Gough @ 2003-05-27 9:15 UTC (permalink / raw)
To: 'gcc@gcc.gnu.org'; +Cc: 'Alexandre Courbot'
Hi all,
I am hoping somebody will be able to helpl me with this. I am trying to
target a new architecure using gcc-3.2.2. I am trying to do this by
modifying the target files which were written for gcc-2.95. I understand
these target files and its architecture is similar to my own. I already had
to modify some macros using the target hooks. (thanks Alex for that).
Now however I get the following error with the file c-decl.c. I have an
inkling that it has something to do with a target macro being modified since
gcc -2.95. Anyway this is the error I get:
from /home/rgough/gcc-3.2.2/gcc/c-errors.c:22:
/home/rgough/gcc-3.2.2/gcc/config/npe/npe.h:47: warning: function
declaration isn't a prototype
In file included from config.h:16,
from /home/rgough/gcc-3.2.2/gcc/c-lex.c:22:
/home/rgough/gcc-3.2.2/gcc/config/npe/npe.h:47: warning: function
declaration isn't a prototype
In file included from config.h:16,
from /home/rgough/gcc-3.2.2/gcc/c-pragma.c:22:
/home/rgough/gcc-3.2.2/gcc/config/npe/npe.h:47: warning: function
declaration isn't a prototype
In file included from config.h:16,
from /home/rgough/gcc-3.2.2/gcc/c-decl.c:29:
/home/rgough/gcc-3.2.2/gcc/config/npe/npe.h:47: warning: function
declaration isn't a prototype
/home/rgough/gcc-3.2.2/gcc/c-decl.c: In function `get_parm_info':
/home/rgough/gcc-3.2.2/gcc/c-decl.c:5360: parse error before '(' token
/home/rgough/gcc-3.2.2/gcc/c-decl.c: In function `store_parm_decls':
/home/rgough/gcc-3.2.2/gcc/c-decl.c:6710: parse error before '(' token
make[1]: *** [c-decl.o] Error 1
make: *** [all-gcc] Error 2
What are the differences between gcc-2.95 and gcc-3.2.2. Are these
differences documented and if so where? Thanks for all the help. Any
comments / suggestions would be warmly appreciated.
Rgds
Roger
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2003-05-27 9:15 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-05-27 9:15 Macros being updated?? Roger.Gough
2003-05-27 9:15 ` Alexandre Courbot
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).