public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/58267] New: Alignment specifier allowed within array declarator;
@ 2013-08-29 3:23 rohan at rohanlean dot de
2013-10-15 17:49 ` [Bug c/58267] " mpolacek at gcc dot gnu.org
2013-10-17 8:15 ` mpolacek at gcc dot gnu.org
0 siblings, 2 replies; 3+ messages in thread
From: rohan at rohanlean dot de @ 2013-08-29 3:23 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58267
Bug ID: 58267
Summary: Alignment specifier allowed within array declarator;
Product: gcc
Version: 4.8.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: rohan at rohanlean dot de
“char s[_Alignas (int) 7];” is accepted without warnings in strict C11 mode. I
cannot construct that declaration using the grammar in appendix A.2 of the
standard.
>From gcc-bugs-return-428587-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Aug 29 06:41:24 2013
Return-Path: <gcc-bugs-return-428587-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15967 invoked by alias); 29 Aug 2013 06:41:24 -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 15917 invoked by uid 48); 29 Aug 2013 06:41:20 -0000
From: "kcc at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/57316] [4.8/4.9 regression] build failure in libsanitizer
Date: Thu, 29 Aug 2013 06:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kcc at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-57316-4-A08HpWX0aI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-57316-4@http.gcc.gnu.org/bugzilla/>
References: <bug-57316-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: 2013-08/txt/msg01511.txt.bz2
Content-length: 480
http://gcc.gnu.org/bugzilla/show_bug.cgi?idW316
--- Comment #6 from Kostya Serebryany <kcc at gcc dot gnu.org> ---
> Would a fallback implementation of BlockingMutex::{Lock,Unlock}() that uses
> pthread_mutex_*() be sensible here?
That would be non-trivial. We intercept the pthread_ functions so we can't
call them directly. We'll at least need to bypass our own interceptors.
And as I mentioned before, older kernels will likely not work anyway for
a few other reasons.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug c/58267] Alignment specifier allowed within array declarator;
2013-08-29 3:23 [Bug c/58267] New: Alignment specifier allowed within array declarator; rohan at rohanlean dot de
@ 2013-10-15 17:49 ` mpolacek at gcc dot gnu.org
2013-10-17 8:15 ` mpolacek at gcc dot gnu.org
1 sibling, 0 replies; 3+ messages in thread
From: mpolacek at gcc dot gnu.org @ 2013-10-15 17:49 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58267
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2013-10-15
CC| |mpolacek at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot gnu.org
Target Milestone|--- |4.9.0
Ever confirmed|0 |1
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Mine. I wonder whether we want to pedwarn, warn, or error out here.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug c/58267] Alignment specifier allowed within array declarator;
2013-08-29 3:23 [Bug c/58267] New: Alignment specifier allowed within array declarator; rohan at rohanlean dot de
2013-10-15 17:49 ` [Bug c/58267] " mpolacek at gcc dot gnu.org
@ 2013-10-17 8:15 ` mpolacek at gcc dot gnu.org
1 sibling, 0 replies; 3+ messages in thread
From: mpolacek at gcc dot gnu.org @ 2013-10-17 8:15 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58267
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Fixed.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-10-17 8:15 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-08-29 3:23 [Bug c/58267] New: Alignment specifier allowed within array declarator; rohan at rohanlean dot de
2013-10-15 17:49 ` [Bug c/58267] " mpolacek at gcc dot gnu.org
2013-10-17 8:15 ` mpolacek at gcc dot gnu.org
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).