[RTEMS Project] #3425: examples-v2: PowerPC fails to build fat_ramdisk
RTEMS trac
trac at rtems.org
Tue May 8 07:37:03 UTC 2018
#3425: examples-v2: PowerPC fails to build fat_ramdisk
---------------------------+---------------------
Reporter: Joel Sherrill | Owner: (none)
Type: defect | Status: new
Priority: normal | Milestone: 5.1
Component: unspecified | Version: 5
Severity: normal | Resolution:
Keywords: | Blocked By:
Blocking: |
---------------------------+---------------------
Comment (by Sebastian Huber):
There are a couple of BSPs which use -D flags:
{{{
grep -- -D bsps/*/*/config/*
bsps/arm/rtl22xx/config/rtl22xx_t.cfg:#CPU_CFLAGS += -mthumb-interwork -D
__THUMB_INTERWORK__ -mthumb
bsps/arm/rtl22xx/config/rtl22xx_t.cfg:#CPU_ASFLAGS += -D
__THUMB_INTERWORK__ -mthumb-interwork
bsps/arm/smdk2410/config/smdk2410.cfg:CPU_CFLAGS = -mcpu=arm920t
-DCPU_S3C2410
bsps/powerpc/beatnik/config/beatnik.cfg:CPU_CFLAGS = -mcpu=7400
-D__ppc_generic
bsps/powerpc/haleakala/config/haleakala.cfg:CPU_CFLAGS = -mcpu=405
-Dppc405
bsps/powerpc/motorola_powerpc/config/mcp750.cfg:CPU_CFLAGS = -mcpu=750
-Dmpc750
bsps/powerpc/motorola_powerpc/config/mtx603e.cfg:CPU_CFLAGS = -mcpu=603e
-Dppc603e
bsps/powerpc/motorola_powerpc/config/mvme2100.cfg:CPU_CFLAGS = -mcpu=603e
-Dppc603e
bsps/powerpc/motorola_powerpc/config/qemuprep-altivec.cfg:CPU_CFLAGS =
-mcpu=7400 -mmultiple -mstring -mstrict-align -D__ppc_generic
bsps/powerpc/motorola_powerpc/config/qemuprep.cfg:CPU_CFLAGS =
-mcpu=powerpc -mmultiple -mstring -mstrict-align -D__ppc_generic
bsps/powerpc/mpc55xxevb/config/mpc55xx.inc: -D__ppc_generic -mstrict-
align
bsps/powerpc/mpc8260ads/config/mpc8260ads.cfg:CPU_CFLAGS = -mcpu=603e
-mstrict-align -Dmpc8260 \
bsps/powerpc/mvme3100/config/mvme3100.cfg:CPU_CFLAGS = -mcpu=powerpc
-msoft-float -D__ppc_generic
bsps/powerpc/mvme5500/config/mvme5500.cfg:CPU_CFLAGS = -mcpu=7450
-mtune=7450 -Dmpc7455
bsps/powerpc/psim/config/psim.cfg:CPU_CFLAGS = -meabi -mcpu=603e
-msdata=sysv -fno-common -Dppc603e
bsps/powerpc/qemuppc/config/qemuppc.cfg:CPU_CFLAGS = -mcpu=603e -Dppc603e
bsps/powerpc/qoriq/config/qoriq_e6500_32.cfg: -D__ppc_generic
bsps/powerpc/qoriq/config/qoriq_e6500_64.cfg: -D__ppc_generic
bsps/powerpc/qoriq/config/qoriq.inc: -D__ppc_generic
bsps/powerpc/ss555/config/ss555.cfg:CPU_CFLAGS = -mcpu=$(GCC_CPU_MODEL)
-Dmpc555
bsps/powerpc/t32mppc/config/t32mppc.cfg: -D__ppc_generic
bsps/powerpc/tqm8xx/config/tqm8xx.inc:CPU_CFLAGS = -mcpu=860 -Dmpc860 \
bsps/powerpc/virtex4/config/virtex4.cfg:CPU_CFLAGS = -mcpu=405 -Dppc405
bsps/powerpc/virtex5/config/virtex5.cfg:CPU_CFLAGS = -mcpu=440 -Dppc440
-msoft-float
bsps/powerpc/virtex/config/virtex.cfg:CPU_CFLAGS = -mcpu=403 -Dppc405
-meabi -msdata=sysv -fno-common
bsps/sparc64/niagara/config/niagara.cfg:CPU_CFLAGS = -mcpu=niagara -DSUN4V
bsps/sparc64/usiii/config/usiii.cfg:CPU_CFLAGS = -mcpu=ultrasparc3 -DUS3
-DSUN4U
}}}
We should ban the use of command line defines.
Getting rid of the `-D__ppc_generic` is easy. Getting rid of the
`-Dppc405`, etc. is more difficult and there is some interaction with the
GCC specs:
{{{
#undef CPP_OS_DEFAULT_SPEC
#define CPP_OS_DEFAULT_SPEC "\
%{!mcpu*: %{!Dppc*: %{!Dmpc*: -Dmpc750} } }\
%{mcpu=403: %{!Dppc*: %{!Dmpc*: -Dppc403} } } \
%{mcpu=505: %{!Dppc*: %{!Dmpc*: -Dmpc505} } } \
%{mcpu=601: %{!Dppc*: %{!Dmpc*: -Dppc601} } } \
%{mcpu=602: %{!Dppc*: %{!Dmpc*: -Dppc602} } } \
%{mcpu=603: %{!Dppc*: %{!Dmpc*: -Dppc603} } } \
%{mcpu=603e: %{!Dppc*: %{!Dmpc*: -Dppc603e} } } \
%{mcpu=604: %{!Dppc*: %{!Dmpc*: -Dmpc604} } } \
%{mcpu=750: %{!Dppc*: %{!Dmpc*: -Dmpc750} } } \
%{mcpu=821: %{!Dppc*: %{!Dmpc*: -Dmpc821} } } \
%{mcpu=860: %{!Dppc*: %{!Dmpc*: -Dmpc860} } } \
%{mcpu=8540: %{!Dppc*: %{!Dmpc*: -Dppc8540} } } \
%{mcpu=e6500: -D__PPC_CPU_E6500__}"
}}}
--
Ticket URL: <http://devel.rtems.org/ticket/3425#comment:6>
RTEMS Project <http://www.rtems.org/>
RTEMS Project
More information about the bugs
mailing list