[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-gcc-list] Re: optimizer removes volatile pin access code.why?
From: |
Joerg Wunsch |
Subject: |
Re: [avr-gcc-list] Re: optimizer removes volatile pin access code.why? |
Date: |
Mon, 2 Nov 2009 16:16:45 +0100 |
User-agent: |
Mutt/1.5.11 |
As Weddington, Eric wrote:
> And IMHO, I highly doubt that this proposal will be approved. They
> will probably just come back to you and say that there's no need for
> it.
Why not? Why do you think issuing a warning for something that is
known it cannot work would be rejected? If the always_inline
attribute is known to only work for a function declared inline, it
should be legitimate to warn the user about a situation where this
prerequisite is not met.
--
cheers, J"org .-.-. --... ...-- -.. . DL8DTL
http://www.sax.de/~joerg/ NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)
- [avr-gcc-list] Re: optimizer removes volatile pin access code. why?, David Brown, 2009/11/01
- Re: [avr-gcc-list] Re: optimizer removes volatile pin access code. why?, Joerg Wunsch, 2009/11/02
- RE: [avr-gcc-list] Re: optimizer removes volatile pin access code.why?, Weddington, Eric, 2009/11/02
- [avr-gcc-list] Re: optimizer removes volatile pin access code.why?, David Brown, 2009/11/02
- Re: [avr-gcc-list] Re: optimizer removes volatile pin access code.why?, Joerg Wunsch, 2009/11/02
- RE: [avr-gcc-list] Re: optimizer removes volatile pin access code.why?, Weddington, Eric, 2009/11/02
- Re: [avr-gcc-list] Re: optimizer removes volatile pin access code.why?,
Joerg Wunsch <=
- RE: [avr-gcc-list] Re: optimizer removes volatile pin access code.why?, Weddington, Eric, 2009/11/02
- RE: [avr-gcc-list] Re: optimizer removes volatile pin access code.why?, Weddington, Eric, 2009/11/02
- Re: [avr-gcc-list] Re: optimizer removes volatile pin access code.why?, Joerg Wunsch, 2009/11/02
- RE: [avr-gcc-list] Re: optimizer removes volatile pin access code.why?, Weddington, Eric, 2009/11/02