Re: [avr-gcc-list] Timer0 interrupt on Mega128

2009-04-21 Thread Jan Menzel
Hi! Many thanks for this hint. Yes, the code was not ideal in that point. I now setup a completely new project with just the lines below and - as expected - the flags are set correctly. Then I started putting back the other code I previously had and found, the the sequence of changing

Re: [avr-gcc-list] avr superoptimizer

2009-04-21 Thread Georg-Johann Lay
Sean D'Epagnier schrieb: Hi, On 4/20/09, Georg-Johann Lay a...@gjlay.de wrote: Hi Sean, as far as I understand, your tool runs on asm code, i.e. you map short sequences of asm instructions (which must not contain code labels) to other instruction sequences. Right, and it's far from

[avr-gcc-list] Optimisation of bit set/clear in uint32_t

2009-04-21 Thread Dale Whitfield
Hi, All this talk of super-optimisers, etc. brings this issue I've had, to the fore again. Perhaps there are suggestions on how to encourage the compiler to do the optimisations rather than having to hand-code to get the best result. Take this code: volatile uint32_t status; static

[avr-gcc-list] GCC 4.4.0

2009-04-21 Thread Weddington, Eric
Hi All, Special note to toolchain distribution maintainers, and people who build the toolchain themselves: GCC 4.4.0 will soon be released (within days). One of the major new features of the 4.4 series is a new Integrated Register Allocator (IRA) for all ports, including the AVR. While some

Re: [avr-gcc-list] Optimisation of bit set/clear in uint32_t

2009-04-21 Thread Georg-Johann Lay
Dale Whitfield schrieb: Hi, All this talk of super-optimisers, etc. brings this issue I've had, to the fore again. Perhaps there are suggestions on how to encourage the compiler to do the optimisations rather than having to hand-code to get the best result. There is some work which addresses

[avr-gcc-list] Re: Optimisation of bit set/clear in uint32_t

2009-04-21 Thread David Brown
Dale Whitfield wrote: Hi, All this talk of super-optimisers, etc. brings this issue I've had, to the fore again. Perhaps there are suggestions on how to encourage the compiler to do the optimisations rather than having to hand-code to get the best result. Take this code: volatile uint32_t

Re: [avr-gcc-list] Timer0 interrupt on Mega128

2009-04-21 Thread Joerg Wunsch
Jan Menzel men...@peperoni-light.de wrote: When the system clock is divided, Timer/Counter0 can be used with Asynchronous clock only. (page 37) I didn't know this... Is there any workaround for this? (the datasheet does not say anything...) Switch to an ATmega1281? -- cheers, Jorg