[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: AW: [avr-gcc-list] "so-called-bug" global register variable is brok
Re: AW: [avr-gcc-list] "so-called-bug" global register variable is broken
Thu, 02 Dec 2004 21:39:20 +0100
Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.6) Gecko/20040114
Haase Bjoern (PT-BEU/MKP5) * schrieb:
simply a brief remark:
In my opinion we do not talk about a bug, but we are talking about a specific
problem that cannot
be solved easily by standard GCC.
In my opinion there is no justification to write a "bug" report. Eventually, we could make the
documentation a bit more explicit about this point.
[mailto:address@hidden Auftrag von E. Weddington
Gesendet: Donnerstag, 2. Dezember 2004 16:10
An: address@hidden; Klaus Rudolph
Betreff: Re: [avr-gcc-list] avr-gcc bug: global register variable is
On 1 Dec 2004 at 15:48, Klaus Rudolph wrote:
it is impossible to define a global register variable in avr-gcc.
The register is used by the compiler on some places and it is really not
Any idea for a workaround? I need some register vars for interrupt handler
Is there allready a patch available or is this maybe fixed in current CVS
head of release 4.0 in gcc sources?
AFAIK, there's nothing new in the avr port itself in this area.
If this is a bug, then *please* submit a GCC bug report on this. That way it can be verified (by
other GCC developers), tracked, and other GCC developers can be aware of this issue.
GCC has this featue and it works with other targets. And the rest of the
generated code "knows" that the
specified register must not used. The register is for example not in the
save list and would not be stored on the stack but
after this it will be used which is definitly a bug.
I dont know why naming this problem a bug is a problem? The code which
is generated is wrong!