Re: [Sdcc-user] "This is probably a compiler bug..." message

2009-10-31 Thread Michel Bouissou
Hi, I've found another situation causing sdcc to spit : « encountered NULL pcop--this is probably a compiler bug... » A line trying to set a variable but using by mistake "==" instead of "=", i.e. somevariable==1; instead of somevariable=1; Then the compiler spits this message without g

Re: [Sdcc-user] "This is probably a compiler bug..." message

2009-10-17 Thread Michel Bouissou
Hi Raphael, Le samedi 17 octobre 2009, Raphael Neider a écrit : > > encountered NULL pcop--this is probably a compiler bug... > > Could you please post the failing source file(s) including all > #include'd files? This would certainly help me debugging your > problem. Meanwhile I solved the proble

Re: [Sdcc-user] "This is probably a compiler bug..." message

2009-10-17 Thread Raphael Neider
Hi Michel, > I'm now getting a more worrying thing : After I defined a (possibly > incorrect due to my limited C experience...) table of structs, when > compiling I get this one : > > sdcc -mpic14 -p16f886 -V --debug -I/myDir/ -c myProg.c > > encountered NULL pcop--this is probably a compiler bu

[Sdcc-user] "This is probably a compiler bug..." message

2009-10-17 Thread Michel Bouissou
(Thanks to Kustaa and "the other Brian" for your latest replies) I'm now getting a more worrying thing : After I defined a (possibly incorrect due to my limited C experience...) table of structs, when compiling I get this one : sdcc -mpic14 -p16f886 -V --debug -I/myDir/ -c myProg.c encountere