http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56439
Georg-Johann Lay changed:
What|Removed |Added
CC||gjl at gcc dot gnu.org
--- C
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56439
--- Comment #7 from Chung-Ju Wu 2013-02-26
03:30:40 UTC ---
Sorry I didn't notice that it is 8-bit register on avr.
I was porting a 32-bit register target and this case is similar to mine.
That's why I have such guess in comment 5.
No
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56439
--- Comment #6 from Robert "Finny" Merrill
2013-02-25 16:39:39 UTC ---
Well other than the fact that it now uses two registers (the registers are
8-bit and ints are 16-bit), no, it does the same thing
register int foo asm ("r30");
voi
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56439
Chung-Ju Wu changed:
What|Removed |Added
CC||jasonwucj at gmail dot com
--- Co
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56439
--- Comment #4 from Robert "Finny" Merrill
2013-02-25 05:46:29 UTC ---
Wouldn't that be a reason /against/ doing this:
mov r24,r4
lsl r24
mov r4,r24
instead of just lsl r4?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56439
--- Comment #3 from Andrew Pinski 2013-02-25
03:53:25 UTC ---
(In reply to comment #2)
> Any specific sections you can point me to? I'd be interested to hear a
> justification for this behavior.
Simple answer, an interrupt can happen an
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56439
--- Comment #2 from Robert "Finny" Merrill
2013-02-25 03:30:47 UTC ---
Any specific sections you can point me to? I'd be interested to hear a
justification for this behavior.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56439
Andrew Pinski changed:
What|Removed |Added
Component|c |target
--- Comment #1 from Andr
