public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/64133] m68k-rtems-gcc generates invalid code.
Date: Mon, 01 Dec 2014 04:08:00 -0000	[thread overview]
Message-ID: <bug-64133-4-VlxalkdQNX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64133-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64133

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Chris Johns from comment #2)
> Thanks for the quick response. The clean trap instruction did confuse me.
> 
> I suppose my work around to move the code into another file stops gcc
> detecting the access. Is this true ?
> 
> I am happy to build our code with the check enabled because accessing 0 is
> something we trap for with MMU targets such as ARM and PowerPC.

It looks like it is just the startup code in the Init5235 function which needs
this extra option, you can use the #pragma's too.
Code like:
        *((short *)(0x00000000)) = 0;

Will produce the trap.


      parent reply	other threads:[~2014-12-01  4:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-01  3:34 [Bug other/64133] New: " chris at contemporary dot net.au
2014-12-01  3:36 ` [Bug other/64133] " pinskia at gcc dot gnu.org
2014-12-01  4:03 ` chris at contemporary dot net.au
2014-12-01  4:08 ` pinskia at gcc dot gnu.org [this message]

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-64133-4-VlxalkdQNX@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).