public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jgreenhalgh 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 13:47:00 -0000 [thread overview]
Message-ID: <bug-64744-4-hUfa7n8EyN@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
jgreenhalgh at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Target|aarch64 |arm-none-linux-gnueabihf
Status|UNCONFIRMED |NEW
Last reconfirmed| |2015-01-23
CC| |jgreenhalgh at gcc dot gnu.org
Host|x86_64 |x86_64-unknown-linux-gnu
Ever confirmed|0 |1
--- Comment #1 from jgreenhalgh at gcc dot gnu.org ---
I can't reproduce this for an AArch64 target.
As far as I can remember, we don't support __attribute__((naked)) for AArch64,
so I would expect the attribute to be ignored (And that is what I see with your
testcase):
gcc foo.c -O0
foo.c:3:1: warning: ‘naked’ attribute directive ignored [-Wattributes]
{
^
However, I can reproduce your bug with an ARM compiler (cross and native), so
I'll confirm the bug, and update the Target field for you.
>From gcc-bugs-return-474566-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 23 13:51:24 2015
Return-Path: <gcc-bugs-return-474566-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 739 invoked by alias); 23 Jan 2015 13:51:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 607 invoked by uid 48); 23 Jan 2015 13:51:08 -0000
From: "dwmw2 at infradead dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/55177] missed optimizations with __builtin_bswap
Date: Fri, 23 Jan 2015 13:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.7.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: dwmw2 at infradead dot org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pinskia at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-55177-4-HEdC03GpIJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55177-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55177-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-01/txt/msg02560.txt.bz2
Content-length: 771
https://gcc.gnu.org/bugzilla/show_bug.cgi?idU177
--- Comment #15 from David Woodhouse <dwmw2 at infradead dot org> ---
More missed optimistions (gcc version 4.9.2 20141101 (Red Hat 4.9.2-1) (GCC))
I see it using movbe for the pointer_abuse() function, but can't see a simple
way to make it use movbe *without* killing kittens.
gcc -march=atom -O2 -x c -o - -S - -Wstrict-aliasing <<EOF
struct pkt {
unsigned char data[10];
};
unsigned or(struct pkt *p)
{
return (p->data[0] << 24) | (p->data[1] << 16) | (p->data[2] << 8) |
p->data[1];
}
unsigned add(struct pkt *p)
{
return (p->data[0] << 24) + (p->data[1] << 16) + (p->data[2] << 8) +
p->data[1];
}
unsigned pointer_abuse(struct pkt *p)
{
return __builtin_bswap32(*(unsigned *)p->data);
}
EOF
next prev parent reply other threads:[~2015-01-23 13:47 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 ` jgreenhalgh at gcc dot gnu.org [this message]
2015-01-23 13:53 ` [Bug middle-end/64744] " 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
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-hUfa7n8EyN@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).