public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/98436] issue with casting member function on linux32 bit only
Date: Fri, 25 Dec 2020 00:20:06 +0000 [thread overview]
Message-ID: <bug-98436-4-MPo3JLTLvK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98436-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98436
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|UNCONFIRMED |RESOLVED
--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Samuel Benjamin from comment #4)
> I got your point, But why is this working with 64bit and other gcc versions
> other than 7.4.0 - 32 bit ?
Because the ABI for x86_64 and i?86 are different. One passes the this
arugment via the stack (i?86) while the other passes it via a register. In the
case for x86_64, the register can be safely ignored.
Again this is undefined code and just happens to work on x86_64.
prev parent reply other threads:[~2020-12-25 0:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-24 9:19 [Bug c++/98436] New: " samuel_benjamin at mentor dot com
2020-12-24 10:04 ` [Bug c++/98436] " pinskia at gcc dot gnu.org
2020-12-24 10:14 ` samuel_benjamin at mentor dot com
2020-12-24 11:15 ` pinskia at gcc dot gnu.org
2020-12-24 12:13 ` samuel_benjamin at mentor dot com
2020-12-24 12:18 ` samuel_benjamin at mentor dot com
2020-12-24 15:52 ` redi at gcc dot gnu.org
2020-12-25 0:20 ` pinskia at gcc dot gnu.org [this message]
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-98436-4-MPo3JLTLvK@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).