hm
thanks,
fixed.
it looks like we've faced with some sort of gcc's voodoo -
if(ull 0xULL) - does not work, but if(ull 0x00ULL) does.
~d
On Sunday 22 December 2002 09:40, Oleg Skydan wrote:
Hi All,
I have found a significant BUG in the simulator.
When you use HW
I guess this one is mostly for Dmitry.
I have been building mspgcc based upon gcc 3.2. Are there any problems
if 3.2.1 is used? It is essentially a bug fix release, so it sounds like
progress. You never can tell until you try, though :-)
The current mspgcc gdb stuff is for gdb 5.1.1.
Steve Underwood wrote:
I guess this one is mostly for Dmitry.
I have been building mspgcc based upon gcc 3.2. Are there any problems
if 3.2.1 is used? It is essentially a bug fix release, so it sounds like
progress. You never can tell until you try, though :-)
I just compiled with
Hi Steve,
On Sunday 22 December 2002 18:12, Steve Underwood wrote:
I guess this one is mostly for Dmitry.
I have been building mspgcc based upon gcc 3.2. Are there any problems
if 3.2.1 is used? It is essentially a bug fix release, so it sounds like
progress. You never can tell until you
Hello, Andrey!
Sunday, December 22, 2002, 8:47:59 PM, you wrote:
AR 1) binutils :
AR 'make install' exits with error like can't find #inst.number when
installing linker.
AR 'cd ld make install' works fine.
Problems in Makefile.in. Fixed, really.
AR 2) gdbproxy:
AR doesn't compile at all,
Hello, Andrey!
Sunday, December 22, 2002, 8:47:59 PM, you wrote:
AR 2) gdbproxy:
AR doesn't compile at all, because it can't find 'stdint.h'. If I copy
stdint.h to gdbproxy src dir, it doesn't compile too, because of 'uint_8
redefinition'.
AR Also, './configure' returns some warnings about
Ok,
Well, I'll check this probably next year :)
Apart from that I see the only advantage is expanding macros.
If you need this feature right now and you're using 'vim', I wrote a plug-in
which expands macro in editor on request. If somebody wants it I can post it
here.
~d
On Sunday 22