public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/64744] ARM: gcc internal compiler error: in store_field, at expr.c:6659
Date: Fri, 23 Jan 2015 14:08:00 -0000	[thread overview]
Message-ID: <bug-64744-4-GRV0WvZ0gb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64744-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from ktkachov at gcc dot gnu.org ---
(In reply to Alexander Basov from comment #4)
> (In reply to ktkachov from comment #3)
> > Confirmed as well on all release branches.
> 
> Ok, If you have no any objections, I'd like to fix it.
> 
> BTW, what gcc should do with such code?

Patches welcome :)
Though I note the ICE only happens at -O0 and disappears if you enable any
optimisation.
According to: https://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html
the 'naked' attribute will omit the prologue/epilogue of the function but it's
supposed to be used only with inline asm and C code is not expected to work
reliably. That being said, we should never ICE...


  parent reply	other threads:[~2015-01-23 14:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23 10:56 [Bug middle-end/64744] New: " coopht at gmail dot com
2015-01-23 13:47 ` [Bug middle-end/64744] " jgreenhalgh at gcc dot gnu.org
2015-01-23 13:53 ` coopht at gmail dot com
2015-01-23 13:56 ` ktkachov at gcc dot gnu.org
2015-01-23 13:58 ` coopht at gmail dot com
2015-01-23 14:08 ` ktkachov at gcc dot gnu.org [this message]
2015-06-02  6:43 ` coopht at gmail dot com
2015-08-03 19:35 ` law at gcc dot gnu.org
2015-08-03 19:36 ` law at redhat 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-64744-4-GRV0WvZ0gb@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).