public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "temporal at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/58192] G++ emits incorrect code when passing enum classes as function parameters
Date: Mon, 19 Aug 2013 16:49:00 -0000 [thread overview]
Message-ID: <bug-58192-4-inpXC9wrDu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58192-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58192
Kenton Varda <temporal at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #30672|0 |1
is obsolete| |
--- Comment #3 from Kenton Varda <temporal at gmail dot com> ---
Created attachment 30673
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30673&action=edit
Demonstration of enum class passing bug (v2)
The first version of my demo was doing slightly weird things with unions in
main(). This was vestigial code from my attempts to narrow down the bug, but
wasn't actually necessary to trigger it. So, I simplified it.
next prev parent reply other threads:[~2013-08-19 16:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 6:27 [Bug c++/58192] New: " temporal at gmail dot com
2013-08-19 6:29 ` [Bug c++/58192] " temporal at gmail dot com
2013-08-19 6:38 ` temporal at gmail dot com
2013-08-19 16:49 ` temporal at gmail dot com [this message]
2013-08-19 16:59 ` paolo.carlini at oracle dot com
2013-08-19 18:09 ` jakub at gcc dot gnu.org
2014-09-18 9:20 ` paolo.carlini at oracle dot com
2014-09-18 10:01 ` jakub at gcc dot gnu.org
2014-09-19 12:10 ` ubizjak at gmail dot com
2014-09-19 13:07 ` ubizjak at gmail dot com
2014-09-19 14:10 ` jakub at gcc dot gnu.org
2014-12-15 14:30 ` ubizjak at gmail dot com
2014-12-15 14:55 ` hjl.tools at gmail dot com
2014-12-15 16:01 ` hjl.tools 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-58192-4-inpXC9wrDu@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).