public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/52461] New: [avr] XMEGA+EBI: RAMPZ clobbered while reading from flash
Date: Fri, 02 Mar 2012 12:19:00 -0000 [thread overview]
Message-ID: <bug-52461-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52461
Bug #: 52461
Summary: [avr] XMEGA+EBI: RAMPZ clobbered while reading from
flash
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
Priority: P3
Component: target
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: gjl@gcc.gnu.org
Target: avr
To read from flash on devices with more than 64KiB of flash, RAMPZ is set
appropriately before using ELPM instruction.
Devices with external bus interface (EBI) use RAMPZ as high part of the RAM
address while reading from RAM.
Thus, and RAM read on EBI device that is performed via Z will fail after data
has been read from Flash.
next reply other threads:[~2012-03-02 12:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 12:19 gjl at gcc dot gnu.org [this message]
2012-03-02 12:23 ` [Bug target/52461] " gjl at gcc dot gnu.org
2012-03-02 12:31 ` gjl at gcc dot gnu.org
2012-03-03 14:13 ` gjl at gcc dot gnu.org
2012-03-06 7:55 ` saturn at quantentunnel dot de
2012-03-06 12:43 ` gjl at gcc dot gnu.org
2012-03-06 12:46 ` gjl at gcc dot gnu.org
2012-03-07 10:14 ` saturn at quantentunnel dot de
2012-03-07 10:34 ` gjl at gcc dot gnu.org
2012-03-07 11:08 ` fbi.sr at gmx dot de
2012-03-07 12:35 ` gjl at gcc dot gnu.org
2012-03-21 13:24 ` gjl at gcc dot gnu.org
2012-03-22 15:14 ` gjl at gcc dot gnu.org
2012-03-22 15:55 ` gjl at gcc dot gnu.org
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=bug-52461-4@http.gcc.gnu.org/bugzilla/ \
--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).