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/49868] Implement named address space to place/access data in flash memory
Date: Tue, 28 Feb 2012 08:45:00 -0000 [thread overview]
Message-ID: <bug-49868-4-uvmnRBxfkv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49868-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49868
--- Comment #16 from Georg-Johann Lay <gjl at gcc dot gnu.org> 2012-02-28 08:44:14 UTC ---
Author: gjl
Date: Tue Feb 28 08:44:08 2012
New Revision: 184614
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=184614
Log:
PR target/49868
PR target/52261
* doc/extend.texi (AVR Named Address Spaces): No more try to fix
address spaces located outside of device flash.
* config/avr/avr.h (base_arch_s): Remove field n_segments.
(mcu_type_s): Add field n_flash.
* config/avr/avr-devices.c (avr_arch_types): Remove .n_segments.
Set .have_elpm and .have_elpmx to 1 for avrxmega4 and avrxmega5.
(AVR_MCU): Add N_FLASH argument.
* config/avr/avr-mcus.def (AVR_MCU): Add initializer for .n_flash.
* config/avr/avr-c.c (avr_cpu_cpp_builtins): Only define built-in
macro __FLASH<n> if that address space makes sense for the device.
* config/avr/avr.c (avr_out_lpm): Don't try to fix address spaces
outside of target flash.
(avr_asm_named_section): Ditto.
(avr_asm_select_section): Ditto.
(avr_addr_space_convert): Ditto.
(avr_emit_movmemhi): Ditto.
(avr_nonconst_pointer_addrspace, avr_pgm_check_var_decl): Error if
address space is outside of device flash.
(avr_insert_attributes): Ditto.
(avr_xload_libgcc_p): Use avr_current_device->n_flash instead of
avr_current_arch->n_segments.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/avr/avr-c.c
trunk/gcc/config/avr/avr-devices.c
trunk/gcc/config/avr/avr-mcus.def
trunk/gcc/config/avr/avr.c
trunk/gcc/config/avr/avr.h
trunk/gcc/doc/extend.texi
next prev parent reply other threads:[~2012-02-28 8:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 12:45 [Bug target/49868] New: " gjl at gcc dot gnu.org
2011-08-04 13:51 ` [Bug target/49868] " gjl at gcc dot gnu.org
2011-10-07 15:23 ` gjl at gcc dot gnu.org
2011-10-07 15:25 ` gjl at gcc dot gnu.org
2011-10-07 15:29 ` gjl at gcc dot gnu.org
2011-10-20 14:36 ` eric.weddington at atmel dot com
2011-10-20 15:19 ` gjl at gcc dot gnu.org
2011-11-15 9:36 ` gjl at gcc dot gnu.org
2011-11-18 17:00 ` gjl at gcc dot gnu.org
2011-11-18 23:08 ` gjl at gcc dot gnu.org
2011-12-06 14:41 ` gjl at gcc dot gnu.org
2011-12-15 16:38 ` gjl at gcc dot gnu.org
2011-12-15 19:09 ` gjl at gcc dot gnu.org
2012-01-10 9:43 ` gjl at gcc dot gnu.org
2012-01-20 12:39 ` gjl at gcc dot gnu.org
2012-01-20 13:01 ` gjl at gcc dot gnu.org
2012-01-24 13:18 ` gjl at gcc dot gnu.org
2012-01-25 19:09 ` gjl at gcc dot gnu.org
2012-02-28 8:45 ` gjl at gcc dot gnu.org [this message]
2012-03-12 17:56 ` gjl at gcc dot gnu.org
2012-03-20 11:49 ` gjl at gcc dot gnu.org
2012-03-22 15:04 ` 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-49868-4-uvmnRBxfkv@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).