public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/66697] Feature request: -mstackrealign and force_align_arg_pointer for x86_64
Date: Mon, 05 Oct 2015 17:40:00 -0000	[thread overview]
Message-ID: <bug-66697-4-MHlTWf7Wr3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66697-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Uroš Bizjak <ubizjak at gmail dot com> ---
Formal patch submission at [1].

Wine people, can someone please test that the patched compiler solves unaligned
stack access, as reported in WineHQ bug?

[1] https://gcc.gnu.org/ml/gcc-patches/2015-10/msg00450.html
>From gcc-bugs-return-498799-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Oct 05 17:47:50 2015
Return-Path: <gcc-bugs-return-498799-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111073 invoked by alias); 5 Oct 2015 17:47:50 -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 111053 invoked by uid 48); 5 Oct 2015 17:47:44 -0000
From: "miyuki at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/67854] Missing diagnostic for passing bool to va_arg
Date: Mon, 05 Oct 2015 17:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: miyuki at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-67854-4-OOGRTE3WyI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67854-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67854-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-10/txt/msg00354.txt.bz2
Content-length: 1910

https://gcc.gnu.org/bugzilla/show_bug.cgi?idg854

--- Comment #2 from Mikhail Maltsev <miyuki at gcc dot gnu.org> ---
(In reply to joseph@codesourcery.com from comment #1)
> I wonder if this is yet another issue with macros from system headers
> (bool being defined in a system header to expand to _Bool) ...

Looks like it is. In gimplify.c:gimplify_va_arg_expr we have:

      /* Unfortunately, this is merely undefined, rather than a constraint
         violation, so we cannot make this an error.  If this call is never
         executed, the program is still strictly conforming.  */
      warned = warning_at (loc, 0,
                           "%qT is promoted to %qT when passed through
%<...%>",
                           type, promoted_type);

And warning_at returns false. Also, for

#include <stdarg.h>
#define BOOL _Bool
void foo(va_list ap)
{
    va_arg(ap, BOOL);
}

GCC outputs:

In file included from test2.c:1:0:
test2.c: In function 'foo':
test2.c:2:14: warning: '_Bool' is promoted to 'int' when passed through '...'
 #define BOOL _Bool
              ^
test2.c:5:16: note: in expansion of macro 'BOOL'
     va_arg(ap, BOOL);
                ^
test2.c:2:14: note: (so you should pass 'int' not '_Bool' to 'va_arg')
 #define BOOL _Bool
              ^
test2.c:5:16: note: in expansion of macro 'BOOL'
     va_arg(ap, BOOL);
                ^
test2.c:2:14: note: if this code is reached, the program will abort
 #define BOOL _Bool
              ^
test2.c:5:16: note: in expansion of macro 'BOOL'
     va_arg(ap, BOOL);

IMHO, it would be more correct to output something like this:

test2.c: In function 'foo':
test2.c:5:16: warning: '_Bool' is promoted to 'int' when passed through '...'
     va_arg(ap, BOOL);
                ^
test2.c:2:14: note: expanded from macro 'BOOL'
 #define BOOL _Bool
              ^


  parent reply	other threads:[~2015-10-05 17:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-29 20:03 [Bug target/66697] New: " bucaneer at gmail dot com
2015-09-29  4:26 ` [Bug target/66697] " austinenglish at gmail dot com
2015-10-04 15:29 ` ubizjak at gmail dot com
2015-10-04 21:23 ` bucaneer at gmail dot com
2015-10-05  9:08 ` ubizjak at gmail dot com
2015-10-05 17:40 ` ubizjak at gmail dot com [this message]
2015-10-05 19:55 ` bucaneer at gmail dot com
2015-10-06  6:40 ` ubizjak at gmail dot com
2015-10-06  9:21 ` ubizjak at gmail dot com
2015-10-06 12:33 ` bucaneer at gmail dot com
2015-10-06 13:45 ` ubizjak at gmail dot com
2015-10-06 16:38 ` bucaneer at gmail dot com
2015-10-06 16:42 ` ubizjak at gmail dot com
2015-10-06 16:53 ` ubizjak at gmail dot com
2015-10-06 23:09 ` bucaneer at gmail dot com
2015-10-07  6:51 ` ubizjak at gmail dot com
2015-10-07 10:49 ` hjl.tools at gmail dot com
2015-10-07 12:13 ` bucaneer at gmail dot com
2015-10-07 12:17 ` hjl.tools at gmail dot com
2015-10-07 12:21 ` ubizjak at gmail dot com
2015-10-07 17:42 ` uros at gcc dot gnu.org
2015-10-12 16:30 ` uros at gcc dot gnu.org
2015-10-12 16:42 ` ubizjak at gmail 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-66697-4-MHlTWf7Wr3@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).