Something screwed up in PROJECT_ROOT or PROJECT_TOPdir

Ralf Corsepius ralf.corsepius at rtems.org
Sun Feb 20 04:15:23 UTC 2005


On Sat, 2005-02-19 at 12:10 -0500, Peter Dufault wrote:
> On Feb 19, 2005, at 11:31 AM, Ralf Corsepius wrote:
> 
> > On Sat, 2005-02-19 at 10:12 -0500, Peter Dufault wrote:
> >
> 
> 
> > * As you seem to be using rtems-cvs, I strongly recommend you to use
> >  maintainer-mode (configure --enable-maintainer-mode).
> 
> Will do.
> 
> >
> > * The CFLAGS you are using are dubious:
> > -mcpu=750 -D__ALTIVEC__ -Wa,-m7450
> >
> > Seems to me as if you are trying to outsmart an older GCC, which does
> > not support the 7450, to "fake" the m7500.
> 
> OK, which gcc should I use?

In an ideal world with a toolchain supporting the 7450 (Should be
functional with GCC-CVS and RTEMS-CVS):
-mcpu=7450 -Dmpc7450

With a toolchain not supporting the 7450 and therefore resorting to a
mpc750 target
-mcpu=750 -Dmpc7450

[
-mcpu=XXX is evaluated by GCC.

-DmpcXXX is used by RTEMS sources and not of any importance to GCC in
most cases (there are exceptions).
]

__ALTIVEC__ is a GCC internal define you should not pass explicitly
anywhere. GCC sets it, if the target-cpu implies altivec support.
It GCC doesn't set it, the target-cpu doesn't support altivec, so you
will have to try getting away without it.

[-mcpu=7450 implies -D__ALTIVEC__ and -maltivec, while -mcpu=750 does
not]

Ralf





More information about the users mailing list