public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/34786]  New: [avr] at86rf401 device needs to be in the avr2 architecture
@ 2008-01-15  3:18 eric dot weddington at atmel dot com
  2008-01-15  4:36 ` [Bug target/34786] " eric dot weddington at atmel dot com
  2008-01-15  7:37 ` eric dot weddington at atmel dot com
  0 siblings, 2 replies; 3+ messages in thread
From: eric dot weddington at atmel dot com @ 2008-01-15  3:18 UTC (permalink / raw)
  To: gcc-bugs

The at86rf401 device needs to be in the avr2 architecture. Currently it is
defined to be in the avr25 architecture, which has the MOVW instruction.
According to binutils, the at86rf401 does not have the MOVW instruction.

The change needs to be in gcc/config/avr/avr.c in the avr_mcu_types array.


-- 
           Summary: [avr] at86rf401 device needs to be in the avr2
                    architecture
           Product: gcc
           Version: 4.2.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: eric dot weddington at atmel dot com
GCC target triplet: avr-*-*


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34786


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug target/34786] [avr] at86rf401 device needs to be in the avr2 architecture
  2008-01-15  3:18 [Bug target/34786] New: [avr] at86rf401 device needs to be in the avr2 architecture eric dot weddington at atmel dot com
@ 2008-01-15  4:36 ` eric dot weddington at atmel dot com
  2008-01-15  7:37 ` eric dot weddington at atmel dot com
  1 sibling, 0 replies; 3+ messages in thread
From: eric dot weddington at atmel dot com @ 2008-01-15  4:36 UTC (permalink / raw)
  To: gcc-bugs



-- 

eric dot weddington at atmel dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
      Known to fail|                            |4.2.2 4.3.0
   Last reconfirmed|0000-00-00 00:00:00         |2008-01-15 01:54:04
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34786


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug target/34786] [avr] at86rf401 device needs to be in the avr2 architecture
  2008-01-15  3:18 [Bug target/34786] New: [avr] at86rf401 device needs to be in the avr2 architecture eric dot weddington at atmel dot com
  2008-01-15  4:36 ` [Bug target/34786] " eric dot weddington at atmel dot com
@ 2008-01-15  7:37 ` eric dot weddington at atmel dot com
  1 sibling, 0 replies; 3+ messages in thread
From: eric dot weddington at atmel dot com @ 2008-01-15  7:37 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #1 from eric dot weddington at atmel dot com  2008-01-15 04:36 -------
My mistake. The AT86RF401 device does have the MOVW instruction, so this is a
binutils bug.


-- 

eric dot weddington at atmel dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34786


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2008-01-15  4:36 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-01-15  3:18 [Bug target/34786] New: [avr] at86rf401 device needs to be in the avr2 architecture eric dot weddington at atmel dot com
2008-01-15  4:36 ` [Bug target/34786] " eric dot weddington at atmel dot com
2008-01-15  7:37 ` eric dot weddington at atmel dot com

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).