FYI,
http://news.com.com/2100-7344_3-5127627.html?tag=nefd_top
-Shawn.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
On Wed, 17 Dec 2003, David C. Chiu wrote:
>
> We're experiencing some unexpected behavior with binary generated with
> the said version of gcc; namely that variables declared to char appear
> to be defaulting to unsigned char.
[ snip ]
> Can someone shed some light on this? (As in, is this "norm
On Wed, 2003-12-17 at 17:02, David C. Chiu wrote:
> We're experiencing some unexpected behavior with binary generated with
> the said version of gcc; namely that variables declared to char appear
> to be defaulting to unsigned char.
>
> #include
> #include
>
> int main( int argc, char** args, ch
Hi All,
I'm getting some funny behaviour on my MPC8260ADS based system.
I am mounting my DiskOnChip 2000 on /mnt/doc. It all seems fine until I try
executing something from it. Trying to execute anything from the doc takes
ages, execution will not occur until a good 2 minutes after you have type
We have developped a board with NPE405 processor with PPC Linux 2.4.20 kernel,
we also have reported various patchs to ibm_ocp device driver, but when we run
a test that outputs via FTP big files of both ethernet interfaces
contemporarly, we observe that there is a period (few seconds) in which
We're experiencing some unexpected behavior with binary generated with
the said version of gcc; namely that variables declared to char appear
to be defaulting to unsigned char.
#include
#include
int main( int argc, char** args, char** envs )
{
char sc;
unsigned char uc;
