Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Hannes Domani <ssbssa@yahoo.de>,
	Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v3][PR gdb/15559] Use thiscall calling convention for class members
Date: Wed, 29 Apr 2020 14:26:59 -0400	[thread overview]
Message-ID: <6e8eebd7-eed7-11ac-dc8a-e1dfe5f2a47d@simark.ca> (raw)
In-Reply-To: <45689522.4534618.1588180764080@mail.yahoo.com>

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.

Thanks,

Simon


  reply	other threads:[~2020-04-29 18:26 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 [this message]
2020-04-30 12:42           ` Hannes Domani

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=6e8eebd7-eed7-11ac-dc8a-e1dfe5f2a47d@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=ssbssa@yahoo.de \
    /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