public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "terry.guo at arm dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/59826] New: ICE caused by mishandling PLD rtx on ARM cortex-m4 target Date: Wed, 15 Jan 2014 12:16:00 -0000 [thread overview] Message-ID: <bug-59826-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59826 Bug ID: 59826 Summary: ICE caused by mishandling PLD rtx on ARM cortex-m4 target Product: gcc Version: 4.8.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: terry.guo at arm dot com Created attachment 31840 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31840&action=edit case to reproduce the ICE When use upstream 4.8 gcc to compile attached case with command: "arm-none-eabi-gcc -mthumb -fprefetch-loop-arrays crash.c -O2 -S -mcpu=cortex-m4", we will get ICE: crash.c: In function 'genxScrubText': crash.c:32:1: internal compiler error: in reg_overlap_mentioned_p, at rtlanal.c:1469 } ^ The option -fprefetch-loop-arrays causes gcc to generate rtx for ARM PLD instruction like: (insn 99 100 105 10 (prefetch (plus:SI (reg/v/f:SI 3 r3 [orig:143 last ] [143]) (const_int 34 [0x22])) (const_int 0 [0]) (const_int 3 [0x3])) 343 {prefetch} (nil)) When check data dependencies between this rtx and others, gcc mishandles it as a normal SET rtx and thus end up with ICE. Trunk gcc hasn't such issue due to code improvement at http://gcc.gnu.org/ml/gcc-patches/2013-11/msg00533.html.
next reply other threads:[~2014-01-15 12:16 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-15 12:16 terry.guo at arm dot com [this message] 2014-01-16 4:10 ` [Bug target/59826] " terry.guo at arm 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-59826-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: 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).