This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/35073] illegal opcode movw for mcu avr3
- From: "Rudolf dot Leitgeb at gmx dot at" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 11 Feb 2008 17:48:53 -0000
- Subject: [Bug target/35073] illegal opcode movw for mcu avr3
- References: <bug-35073-9565@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #5 from Rudolf dot Leitgeb at gmx dot at 2008-02-11 17:48 -------
Subject: Re: illegal opcode movw for mcu avr3
Please note, that this bug is also apparent in the production
version of gcc 4.2.3. This is the specific reason why I posted
a supposed copy of the original bug report: the original bug
report mentioned version 4.3, and I was unable to add version 4.2.3
to the list of affected gcc releases.
Hopefully I can get around to try out the patch tonight. Please
note that while it's perfectly acceptable for a snapshot release
like gcc 4.3 to require patched binutils, this should not happen
for a standard release version of gcc IMHO. AFAIK there is no
binutils production release newer than 2.18 at the moment.
Cheers,
Rudi
Am 11.02.2008 um 18:17 schrieb corsepiu at gcc dot gnu dot org:
>
>
> ------- Comment #4 from corsepiu at gcc dot gnu dot org 2008-02-11
> 17:17 -------
> The binutils patch mentioned in comment#2 seems to fix this issue.
>
> Today's gcc-trunk using binutils-2.18 with the patch applied
> doesn't expose
> this breakdown anymore.
>
> => The cause for this breakdown was using insufficient binutils.
> Bootstrapping/building gcc-4.3 for the avr requires binutils >
> 2.18.
>
>
> --
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35073
>
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35073