public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "airbak.li at huawei dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/63803] New: When GCC 4.9.2 compile with option -O2, the target is error.
Date: Mon, 10 Nov 2014 09:57:00 -0000	[thread overview]
Message-ID: <bug-63803-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 63803
           Summary: When GCC 4.9.2 compile with option -O2, the target is
                    error.
           Product: gcc
           Version: 4.9.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: airbak.li at huawei dot com

The option -fisolate-erroneous-paths-dereference in -O2 causes it.
1.file b.c:
int main()
{
    //volatile unsigned int
    //unsigned int orgin = *((int *)0);   //ok
    //unsigned int orgin = *((unsigned int *)0); //ok
    unsigned int orgin = *((volatile unsigned int *)0);   //nok
    printf("---");

    return 0;
}

2.compile:
arm-none-eabi-gcc --specs=nosys.specs -O2 b.c -o b
or
arm-none-eabi-gcc --specs=nosys.specs -O1 -fisolate-erroneous-paths-dereference
b.c -o b

3.asm
00008210 <main>:
    8210:    e3a03000     mov    r3, #0
    8214:    e5933000     ldr    r3, [r3]
    8218:    e7f000f0     udf    #0


4.question:
Why it is "udf    #0"?  
Is it a BUG?
Please help me, thanks!


             reply	other threads:[~2014-11-10  9:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-10  9:57 airbak.li at huawei dot com [this message]
2014-11-10 10:04 ` [Bug c/63803] " mpolacek at gcc dot gnu.org
2014-11-10 10:06 ` pinskia at gcc dot gnu.org
2014-11-10 11:14 ` airbak.li at huawei dot com
2014-11-10 11:18 ` ktkachov at gcc dot gnu.org
2014-11-10 11:21 ` mpolacek at gcc dot gnu.org
2014-11-10 11:36 ` glisse at gcc dot gnu.org
2014-11-10 11:49 ` airbak.li at huawei 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=bug-63803-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).