public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "P at draigBrady dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/66661] incorrect memory access in optimization with flexible array member
Date: Thu, 25 Jun 2015 11:04:00 -0000 [thread overview]
Message-ID: <bug-66661-4-bhwBJEaokY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66661-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66661
--- Comment #9 from Pádraig Brady <P at draigBrady dot com> ---
I'm not understanding completely TBH. Are flexible array members not special?
Should the optimizations be restricted on access through the flexible array,
because I presume most/all existing allocation code is not considering this
alignment/padding issue. I certainly didn't notice any examples when looking
into a workaround which I came up with independently. For my reference there
are some notes RE GCC's divergence from C99 re padding and flexi arrays at:
https://sites.google.com/site/embeddedmonologue/home/c-programming/data-alig
>From gcc-bugs-return-490190-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jun 25 11:49:08 2015
Return-Path: <gcc-bugs-return-490190-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46295 invoked by alias); 25 Jun 2015 11:49:06 -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 46234 invoked by uid 48); 25 Jun 2015 11:49:02 -0000
From: "mwahab at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/64783] -march=armv8.1-a should be supported
Date: Thu, 25 Jun 2015 11:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mwahab at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mwahab at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-64783-4-ZwkLsxjkSd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64783-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64783-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-06/txt/msg02522.txt.bz2
Content-length: 1183
https://gcc.gnu.org/bugzilla/show_bug.cgi?idd783
--- Comment #3 from mwahab at gcc dot gnu.org ---
I've just noticed this has been assigned to me. Support for -march=armv8.1-a
has been added to the Aarch64 backend, the ARM backend is still to be done.
Author: mwahab
Date: Tue Jun 16 13:38:37 2015
New Revision: 224519
URL: https://gcc.gnu.org/viewcvs?rev"4519&root=gcc&view=rev
Log:
2015-06-16 Matthew Wahab <matthew.wahab@arm.com>
* config/aarch64/aarch64-arches.def: Add "armv8.1-a".
* config/aarch64/aarch64-options-extensions.def: Update "fP",
"simd" and "crypto". Add "lse", "pan", "lor" and "rdma".
* gcc/config/aarch64/aarch64.h (AARCH64_FL_LSE): New.
(AARCH64_FL_PAN): New.
(AARCH64_FL_LOR): New.
(AARCH64_FL_RDMA): New.
(AARCH64_FL_FOR_ARCH8_1): New.
* doc/invoke.texi (AArch64 Options): Add "armv8.1-a" to
-march. Add "lse", "pan", "lor", "rdma" to feature modifiers.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/aarch64/aarch64-arches.def
trunk/gcc/config/aarch64/aarch64-option-extensions.def
trunk/gcc/config/aarch64/aarch64.h
trunk/gcc/doc/invoke.texi
next prev parent reply other threads:[~2015-06-25 11:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 1:25 [Bug c/66661] New: " P at draigBrady dot com
2015-06-25 1:26 ` [Bug c/66661] " P at draigBrady dot com
2015-06-25 2:01 ` [Bug middle-end/66661] " P at draigBrady dot com
2015-06-25 7:54 ` rguenth at gcc dot gnu.org
2015-06-25 11:04 ` P at draigBrady dot com [this message]
2015-06-25 17:13 ` joseph at codesourcery 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-66661-4-bhwBJEaokY@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).