public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Daniel Santos <daniel.santos@pobox.com>
To: JonY <10walls@gmail.com>, Uros Bizjak <ubizjak@gmail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
	Jan Hubicka <hubicka@ucw.cz>,
	Sandra Loosemore <sandra@codesourcery.com>
Subject: Re: [RFC] [PATCH v3 0/8] [i386] Use out-of-line stubs for ms_abi pro/epilogues
Date: Sat, 11 Feb 2017 07:24:00 -0000	[thread overview]
Message-ID: <5352859a-ea66-1b91-c07c-79c5c56fff4a@pobox.com> (raw)
In-Reply-To: <5b7e6964-3875-55c2-caea-a95f36a466bb@gmail.com>

On 02/10/2017 06:20 PM, JonY wrote:
> On 02/10/2017 05:23 PM, Daniel Santos wrote:
>> On 02/10/2017 05:34 AM, JonY wrote:
>>> Hi,
>>> mingw-w64 itself does not use any ms_abi/sysv_abi marked functions
>>> internally, so it should be unaffected. I don't think Cygwin uses any
>>> either, but I need to double check.
>> Of course, ms_abi is gcc's default on Windows so it would be sysv_abi
>> functions.  I'm *guessing* that just about everything with Cygwin is
>> built for Windows, but it would also make sense if (in some odd case) a
>> binary built with sysv_abi is used by something and that library or
>> program makes the ABI transition when using said hypothetical library.
>> Even in these cases, I would not anticipate a problem, although any use
>> of SEH would inhibit the optimization.  Of course, I haven't *tested*
>> this, so I'm only speaking from what I know. :)
>>
> Cygwin has internal functions marked ms_abi but none with sysv_abi, so
> it will be unaffected by this change. Most 64bit mingw-w64 toolchains
> are built with SEH for exception handling though, but since it is
> disabled, it shouldn't break anything.
>
> If its not too much to ask, please do a gcc build targeting 32bit/64bit
> mingw-w64 and Cygwin, it'll make solid evidence that the changes do not
> break the compiler.
>
> Thanks.

Will do. I'll even run a query afterwards and see if anything in Cygwin 
actually makes cross-ABI functions just for the sake of our collective 
curiosity. It's always nice to know.  It is important that I make sure 
we don't break anything in Cygwin, being that I've mostly been thinking 
about Wine.

Daniel

  reply	other threads:[~2017-02-11  3:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-07 18:34 Daniel Santos
2017-02-07 18:36 ` [PATCH 3/8] [i386] Adds class xlouge_layout and new fields to struct machine_function Daniel Santos
2017-02-07 18:36 ` [PATCH 2/8] [i386] Add option -moutline-msabi-xlogues Daniel Santos
2017-02-08 23:28   ` Bernhard Reutner-Fischer
2017-02-10  4:43     ` Daniel Santos
2017-02-10 16:54       ` Sandra Loosemore
2017-02-10 17:32         ` Daniel Santos
2017-04-01 22:37         ` Daniel Santos
2017-02-07 18:36 ` [PATCH 4/8] [i386] Modify ix86_save_reg to optionally omit stub-managed registers Daniel Santos
2017-02-07 18:37 ` [PATCH 6/8] [i386] Add patterns and predicates foutline-msabi-xlouges Daniel Santos
2017-02-07 18:37 ` [PATCH 1/8] [i386] Minor refactoring Daniel Santos
2017-02-07 18:37 ` [PATCH 7/8] [i386] Add msabi pro/epilogue stubs to libgcc Daniel Santos
2017-02-07 18:37 ` [PATCH 5/8] [i386] Modify ix86_compute_frame_layout for foutline-msabi-xlogues Daniel Santos
2017-02-10 10:32 ` [RFC] [PATCH v3 0/8] [i386] Use out-of-line stubs for ms_abi pro/epilogues Uros Bizjak
2017-02-10 11:34   ` JonY
2017-02-10 17:20     ` Daniel Santos
2017-02-11  0:30       ` JonY
2017-02-11  7:24         ` Daniel Santos [this message]
2017-03-13 18:40         ` Daniel Santos
2017-03-10  4:42     ` Daniel Santos
2017-03-30 17:55       ` Daniel Santos
2017-03-30 23:28         ` JonY
2017-02-10 17:55   ` Daniel Santos

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=5352859a-ea66-1b91-c07c-79c5c56fff4a@pobox.com \
    --to=daniel.santos@pobox.com \
    --cc=10walls@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=sandra@codesourcery.com \
    --cc=ubizjak@gmail.com \
    /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).