From: Dr R. W. <R.W...@18...> - 2001-02-27 09:27:46
|
Johan, > > need to be symbols such as i8051, __i8051__, z80 __z80__ etc. (given that > > sdcpp is actually GNU cpp I propose that we go with the GCC naming > standard) > > depending on which -m option is chosen. This will necessitate some > changes > > to SDCCmain.c > > Althoul the SDCC_<target> was already defined, I added __<target> during a > cleanup process. Although there is a problem with the "sdcc -E -dM x.c" command so that it is not currently possible to check the pre-processor symbols, I had a peek at the source code and saw these entries being made. I wonder whether __target__ should also be added so as to give consistency with the style that GCC is bringing to the world (since SDCC uses GNU cpp). Using Cygwin GCC as an example: 501 PAN:russel |> gcc -E -dM - < /dev/null #define __i386__ 1 #define __i386 1 #define __i686 1 #define __GNUC_MINOR__ 95 #define WINNT 1 #define __declspec(x) __attribute__((x)) #define pentiumpro 1 #define __CYGWIN__ 1 #define __pentiumpro 1 #define _X86 1 #define i386 1 #define i686 1 #define __pentiumpro__ 1 #define _WIN32 1 #define __stdcall __attribute__((__stdcall__)) #define __i686__ 1 #define __GNUC__ 2 #define __cdecl __attribute__((__cdecl__)) #define __STDC__ 1 #define __CYGWIN32__ 1 #define unix 1 502 PAN:russel |> Russel. ==================================================================== Dr Russel Winder Chief Technology Officer OneEighty Software Ltd Tel: +44 20 8263 2329 The Lansdowne Building Fax: +44 20 8263 6314 2 Lansdowne Road R.W...@18... Croydon, Surrey CR9 2ER, UK http://www.180sw.com ==================================================================== Under the Regulation of Investigatory Powers (RIP) Act 2000 together with any and all Regulations in force pursuant to the Act One Eighty Software Ltd reserves the right to monitor any or all incoming or outgoing communications as provided for under the Act |