From: Hannes Domani <ssbssa@yahoo.de>
To: Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v3][PR gdb/15559] Use thiscall calling convention for class members
Date: Thu, 30 Apr 2020 12:42:18 +0000 (UTC) [thread overview]
Message-ID: <1901697675.5346744.1588250538897@mail.yahoo.com> (raw)
In-Reply-To: <6e8eebd7-eed7-11ac-dc8a-e1dfe5f2a47d@simark.ca>
Am Mittwoch, 29. April 2020, 20:27:02 MESZ hat Simon Marchi <simark@simark.ca> Folgendes geschrieben:
> On 2020-04-29 1:19 p.m., Hannes Domani via Gdb-patches wrote:
> > Am Mittwoch, 29. April 2020, 18:49:32 MESZ hat Hannes Domani via Gdb-patches <gdb-patches@sourceware.org> Folgendes geschrieben:
> >
> >> Am Mittwoch, 29. April 2020, 18:45:35 MESZ hat Simon Marchi <simark@simark.ca> Folgendes geschrieben:
> >>
> >>>> @@ -234,6 +264,8 @@ i386_windows_init_abi (struct gdbarch_info info, struct gdbarch *gdbarch)
> >>>> {
> >>>> i386_windows_init_abi_common (info, gdbarch);
> >>>> windows_init_abi (info, gdbarch);
> >>>> +
> >>>> + set_gdbarch_push_dummy_call (gdbarch, i386_windows_push_dummy_call);
> >>>> }
> >>>
> >>> Just to be sure, this call convention does not apply to Cygwin programs?
> >>
> >>
> >> I don't really know, but you're right, I should find out.
> >> I will install & test with a cygwin compiler tomorrow.
> >
> > Installing cygwin went faster than I expected.
> >
> > And yes, cygwin does NOT use thiscall calling convention.
> > That just makes me more glad that now there exists a distinction between
> > cygwin & non-cygwin programs in gdb.
>
> Ok, the patch LGTM then.
Pushed, thanks.
Hannes
prev parent reply other threads:[~2020-04-30 12:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200429134808.3642-1-ssbssa.ref@yahoo.de>
2020-04-29 13:48 ` Hannes Domani
2020-04-29 16:45 ` Simon Marchi
2020-04-29 16:49 ` Hannes Domani
2020-04-29 17:19 ` Hannes Domani
2020-04-29 18:26 ` Simon Marchi
2020-04-30 12:42 ` Hannes Domani [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=1901697675.5346744.1588250538897@mail.yahoo.com \
--to=ssbssa@yahoo.de \
--cc=gdb-patches@sourceware.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