public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sbence92 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/94770] class with empty base passed incorrectly with -std=c++17 on mingw
Date: Mon, 27 Apr 2020 07:50:27 +0000	[thread overview]
Message-ID: <bug-94770-4-AUegPuQrPa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94770-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Bence Szabó <sbence92 at gmail dot com> ---
> Ah, then it is not c++14 vs. c++17 ABI incompatibility, but some bug in
> va_arg passing of such classes for mingw.

It seems so. In t032 I got rid of the crashing tests (30, 56, 77, 80, 89, 100,
117, 134, 162, 171, 174, 191, 250 all of them are the second variadic test
case) and the rest of the tests pass in t032. Same in t059: 2998, 2828 crash on
2nd variadic test the rest passes.

Sorry for misleading bug report, I saw the same test cases fail as the
mentioned reports, didn't know the reason is so different.

  parent reply	other threads:[~2020-04-27  7:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-26  9:17 [Bug target/94770] New: " sbence92 at gmail dot com
2020-04-26 15:15 ` [Bug target/94770] " jakub at gcc dot gnu.org
2020-04-26 20:44 ` sbence92 at gmail dot com
2020-04-26 20:45 ` sbence92 at gmail dot com
2020-04-26 21:26 ` sbence92 at gmail dot com
2020-04-26 21:28 ` jakub at gcc dot gnu.org
2020-04-27  7:50 ` sbence92 at gmail dot com [this message]
2020-04-27  9:51 ` jakub at gcc dot gnu.org
2020-04-27 10:49 ` redi at gcc dot gnu.org
2020-04-27 10:50 ` redi at gcc dot gnu.org
2020-04-27 11:04 ` jakub at gcc dot gnu.org
2020-04-27 11:41 ` jakub at gcc dot gnu.org
2020-04-27 11:48 ` jakub at gcc dot gnu.org
2020-04-27 12:27 ` jakub at gcc dot gnu.org
2020-05-09 19:37 ` sbence92 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-94770-4-AUegPuQrPa@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).