On 08/02/2012 20:17, Vidya Praveen wrote:
Hi
Things change in the compiler and there are often cases which are not
covered due to several reasons. it's not uncommon to see something that
works in a earlier version stops working later. It will be great if you
could reduce your test case and/or find out what is going wrong and post
this in avr-gcc-list.If you think the problem is specific to AVR
Toolchain, I recommend you to contact the Atmel support. Thanks
You are probably better off posting such information to the avr-gcc
mailing list rather than Atmel support. I have nothing to complain
about regarding Atmel's support team - I have certainly encountered far
worse - but by posting to the avr-gcc mailing list you get the
information directly to the people responsible for the avr port of gcc,
and you also inform other avr-gcc users.
mvh.,
David
Regards
Vidya Praveen
On Wed, Feb 8, 2012 at 9:42 PM, Daved <dehav...@verizon.net
<mailto:dehav...@verizon.net>> wrote:
Thanks for the responses guys. It's not always clear where to post
problems with this stuff.
I have since done a general web search for the problem and did find
a code correction for w5100.h. I was about to try it when my Arduino
ATmega328P chip went bad and I am now waiting for another one in the
mail. It's still puzzling why an earlier complier version works
while a newer one does not.
Anyway, I have already spent way too much time tracking this down so
other than testing the code correction when I get a new chip, I am
going to let it rest
Dave
----- Original Message ----- From: "Joerg Wunsch"
<j...@uriah.heep.sax.de <mailto:j...@uriah.heep.sax.de>>
To: "David Brown" <da...@westcontrol.com <mailto:da...@westcontrol.com>>
Cc: "David DeHaven" <dehav...@verizon.net
<mailto:dehav...@verizon.net>>; <avr-libc-dev@nongnu.org
<mailto:avr-libc-dev@nongnu.org>>
Sent: Wednesday, February 08, 2012 5:46 AM
Subject: Re: [avr-libc-dev] [bug #35467] Not sure this the right
plce to submit this but...
As David Brown wrote:
For future reference, remember that when you make a bug
report, the
"summary" is critical - it lets people see at a glance what
the problem
is, it is used for searching for similar problems, and is
used in
reports of outstanding issues.
Thanks for the reminder, I changed the subject in the bug
tracker even
though it's closed, for the benefit of those who are searching
old bug
reports.
--
cheers, J"org .-.-. --... ...-- -.. . DL8DTL
http://www.sax.de/~joerg/ NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)
_________________________________________________
AVR-libc-dev mailing list
AVR-libc-dev@nongnu.org <mailto:AVR-libc-dev@nongnu.org>
https://lists.nongnu.org/__mailman/listinfo/avr-libc-dev
<https://lists.nongnu.org/mailman/listinfo/avr-libc-dev>
_______________________________________________
AVR-libc-dev mailing list
AVR-libc-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/avr-libc-dev
