public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Rudolf dot Leitgeb at gmx dot at" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/35073] illegal opcode movw for mcu avr3
Date: Mon, 11 Feb 2008 17:49:00 -0000	[thread overview]
Message-ID: <20080211174853.19090.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35073-9565@http.gcc.gnu.org/bugzilla/>



------- 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


  parent reply	other threads:[~2008-02-11 17:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-04  9:15 [Bug target/35073] New: " corsepiu at gcc dot gnu dot org
2008-02-08 11:27 ` [Bug target/35073] " rguenth at gcc dot gnu dot org
2008-02-11 14:50 ` joel at gcc dot gnu dot org
2008-02-11 16:45 ` manu at gcc dot gnu dot org
2008-02-11 17:18 ` corsepiu at gcc dot gnu dot org
2008-02-11 17:49 ` Rudolf dot Leitgeb at gmx dot at [this message]
2008-02-11 19:26 ` Rudolf dot Leitgeb at gmx dot at
2008-02-11 22:50 ` eric dot weddington at atmel dot com
2008-03-09  5:44 ` eric dot weddington at atmel dot com
2008-07-19 13:06 ` eric dot weddington at atmel dot com
     [not found] <bug-35073-4@http.gcc.gnu.org/bugzilla/>
2011-04-21 10:32 ` gjl at gcc dot gnu.org
2014-02-16 13:15 ` jackie.rosen at hushmail dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080211174853.19090.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).