From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1624 invoked by alias); 11 Feb 2008 19:26:19 -0000 Received: (qmail 1533 invoked by uid 48); 11 Feb 2008 19:25:36 -0000 Date: Mon, 11 Feb 2008 19:26:00 -0000 Message-ID: <20080211192536.1532.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug target/35073] illegal opcode movw for mcu avr3 In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "Rudolf dot Leitgeb at gmx dot at" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2008-02/txt/msg01200.txt.bz2 ------- Comment #6 from Rudolf dot Leitgeb at gmx dot at 2008-02-11 19:25 ------- I just tried the suggested patch against binutils 2.18, gcc 4.2.3 still does not compile. Also, the suggested patch does not apply cleanly against 2.18, although this only affects a .texi file which is not needed for compilation. It does indicate, though, that the patch wa snot meant for binutils 2.18 but some preversion of binutils 2.19 instead. I hope this new version comes of binutils out soon, since 2.18 doesn't know of a platform avr35 :-( Hence gcc 4.2.3 uses avr3 which causes touble. Note: I don't fully understand why the patch doesn't work. I clearly see a line which defines the AVR3 platform to support MOVW, I did a make clean && make && make install of the manually patched binutils before trying gcc again (also with make clean && configure --target=avr && make) Maybe I have to wait for binutils 2.19 before this gets cleared up ... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35073