public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "demiurg_spb at freemail dot ru" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/56263] [avr] Provide strict address-space checking Date: Wed, 13 Mar 2013 06:46:00 -0000 [thread overview] Message-ID: <bug-56263-4-IneDrCibPW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56263-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56263 --- Comment #8 from demiurg_spb at freemail dot ru 2013-03-13 06:46:40 UTC --- (In reply to comment #7) > Sorry? I don't understand you last remark. Are you saying it is trivial to > implement in the avr backend? > No. Implementation is hard work. I mean that if we take (typeof(lhs)==typeof(rhs)) axiom in initialization and assignment: we have no logical problem at all. > Before implementing it, you'll have to specify it. What should do this code? > > const __flash char* f (int i) > { > const __flash char *p = "Hallo" + i; > return p; > } Yes it's not trivial... But it should be equal to next cases: const __flash char* f (int i) { const __flash char *p = "Hallo"; // flash str return &p[i]; } const __flash char* f (int i) { return "Hallo" + i; // flash str } const __flash char* f (int i) { return &"Hallo"[i]; // flash str }
next prev parent reply other threads:[~2013-03-13 6:46 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-09 10:30 [Bug target/56263] New: " gjl at gcc dot gnu.org 2013-02-09 10:31 ` [Bug target/56263] " gjl at gcc dot gnu.org 2013-02-10 12:25 ` demiurg_spb at freemail dot ru 2013-02-11 15:10 ` gjl at gcc dot gnu.org 2013-02-11 15:10 ` gjl at gcc dot gnu.org 2013-02-12 6:48 ` demiurg_spb at freemail dot ru 2013-02-19 17:59 ` gjl at gcc dot gnu.org 2013-02-20 5:54 ` demiurg_spb at freemail dot ru 2013-03-12 11:42 ` gjl at gcc dot gnu.org 2013-03-12 21:21 ` gjl at gcc dot gnu.org 2013-03-13 6:46 ` demiurg_spb at freemail dot ru [this message] 2013-03-22 14:48 ` jakub at gcc dot gnu.org 2013-04-20 5:11 ` 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-56263-4-IneDrCibPW@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: linkBe 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).