* docprobe.c on PowerPC
@ 2002-05-02 6:57 Brendan J Simon
2002-05-02 8:23 ` David Woodhouse
0 siblings, 1 reply; 2+ messages in thread
From: Brendan J Simon @ 2002-05-02 6:57 UTC (permalink / raw)
To: mtd
There a bug in MTD and/or Linux and/or gcc for docprobe on PowerPC
machines. I have a pretty recent linux.2.4.18-pre8 kernel from the
bitkeeper linuxppc_devel archives. It seems that when setting up
doc_locations[] that the #elif defined(__ppc__) is not executed. The
gcc specs file does not mention this definition. I did a gcc -v on a
test file and it seems that -DPPC -D__PPC and -D__PPC__ are defined but
not -D__ppc__. Other architectures in the docprobe.c file use
__alpha__, __i386 __x86_64__, etc. Where do these definitions come from
(or where are they supposed to be defined) ? In GCC, the linux kernel
or should the MTD code use __PPC__ instead ???
Thanks,
Brendan Simon.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: docprobe.c on PowerPC
2002-05-02 6:57 docprobe.c on PowerPC Brendan J Simon
@ 2002-05-02 8:23 ` David Woodhouse
0 siblings, 0 replies; 2+ messages in thread
From: David Woodhouse @ 2002-05-02 8:23 UTC (permalink / raw)
To: brendan.simon; +Cc: mtd
brendan.simon@bigpond.com said:
> Where do these definitions come from (or where are they supposed to
> be defined) ? In GCC, the linux kernel or should the MTD code use
> __PPC__ instead ???
They come from GCC and aren't really expected to be consistent across
architectures. I've changed docprobe.c to use __PPC__. Thanks for pointing
it out. I don't remember where that PPC address came from - perhaps they
should be platform-specific like the Ocelot one, not arch-specific.
--
dwmw2
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-05-02 8:23 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-05-02 6:57 docprobe.c on PowerPC Brendan J Simon
2002-05-02 8:23 ` David Woodhouse
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox