[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-gcc-list] Extremly confusing behaviour... (Suspect compiler?, o
From: |
Keith Gudger |
Subject: |
Re: [avr-gcc-list] Extremly confusing behaviour... (Suspect compiler?, optimization error?) |
Date: |
Wed, 14 May 2003 09:42:55 -0700 (PDT) |
You say you read the FAQ, but I see that your return value is still not
declared volatile.
If you would like us to help you, you must send us the assembly language
produced for this loop.
Try avr-gcc with the -S option to give you the assembly output.
Keith
On 14 May 2003, Mike Panetta wrote:
> A: I already did that.
> B: I am not using the variables you mentioned yet, and they are not
> involved in the code that I am having problems with.
>
> I have read the FAQ (many times, its even where I got the basis for my
> i2c code for this project from), and I know what volatile is for.
>
> The problem I am having is GCC is seemingly IGNORING the return value of
> a function I am calling. Why is it doing that? That is what I need
> help with.
>
> Thanks,
> Mike
>
> Wondering if anyone is actually reading his emails before pushing him at
> the FAQ...
>
> On Wed, 2003-05-14 at 12:17, Joerg Wunsch wrote:
> > Mike Panetta <address@hidden> wrote:
> >
> > > If someone could help me understand my error, I would be greatly
> > > appreciated.
> >
> > Why didn't you follow Keith's advise, and looked into the FAQ? You'll
> > certainly want to declare at least one of your variables to be
> > "volatile", namely SPIByteCounter, but maybe more -- please try to
> > read and understand the FAQ. It would have saved you hours.
> >
> > In case you don't know:
> >
> > http://savannah.nongnu.org/download/avr-libc/doc/avr-libc-user-manual/FAQ.html
> >
> > --
> > J"org Wunsch Unix support
> > engineer
> > address@hidden http://www.interface-systems.de/~j/
> >
> > _______________________________________________
> > avr-gcc-list mailing list
> > address@hidden
> > http://www.avr1.org/mailman/listinfo/avr-gcc-list
>
>
>
> _______________________________________________
> avr-gcc-list mailing list
> address@hidden
> http://www.avr1.org/mailman/listinfo/avr-gcc-list
>
>
>
- [avr-gcc-list] Extremly confusing behaviour..., Mike Panetta, 2003/05/13
- Re: [avr-gcc-list] Extremly confusing behaviour..., Keith Gudger, 2003/05/13
- Re: [avr-gcc-list] Extremly confusing behaviour... (Suspect compiler?, optimization error?), Mike Panetta, 2003/05/14
- Re: [avr-gcc-list] Extremly confusing behaviour... (Suspect compiler?, optimization error?), Joerg Wunsch, 2003/05/14
- Re: [avr-gcc-list] Extremly confusing behaviour... (Suspect compiler?, optimization error?), Mike Panetta, 2003/05/14
- Re: [avr-gcc-list] Extremly confusing behaviour... (Suspect compiler?, optimization error?),
Keith Gudger <=
- Re: [avr-gcc-list] Extremly confusing behaviour... (Suspect compiler?, optimization error?), Mike Panetta, 2003/05/14
- Re: [avr-gcc-list] Extremly confusing behaviour... (Suspectcompiler?, optimization error?), Larry Barello, 2003/05/14
- Re: [avr-gcc-list] Extremly confusing behaviour... (Suspectcompiler?, optimization error?), Mike Panetta, 2003/05/14
- RE: [avr-gcc-list] Extremely confusing behaviour... (Suspectcompiler?,optimization error?), Ralph Mason, 2003/05/14
- Re: [avr-gcc-list] Extremly confusing behaviour... (Suspect compiler?, optimization error?), Joerg Wunsch, 2003/05/14
- Re: [avr-gcc-list] Extremly confusing behaviour... (more detailed explanation of error, believe me its not a volatile thing), Mike Panetta, 2003/05/14
- Re: [avr-gcc-list] Extremly confusing behaviour... (more detailedexplanation of error, believe me its not a volatile thing), Larry Barello, 2003/05/14
- Re: [avr-gcc-list] Extremly confusing behaviour... (more detailedexplanation of error, believe me its not a volatile thing), Mike Panetta, 2003/05/14
- Re: [avr-gcc-list] Extremly confusing behaviour... (more detailed explanation of error, believe me its not a volatile thing), E. Weddington, 2003/05/14
- Re: [avr-gcc-list] Extremly confusing behaviour... (more detailed explanation of error, believe me its not a volatile thing), Mike Panetta, 2003/05/14