This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [patch i386]: PR/39356 name collision of __chkstk

From: "Aaron W. LaFramboise" <aaronavay62 at aaronwl dot com>
To: Kai Tietz <Kai dot Tietz at onevision dot com>
Cc: gcc-patches at gcc dot gnu dot org, Danny Smith <dansmister at gmail dot com>
Date: Tue, 24 Mar 2009 23:07:36 -0500
Subject: Re: [patch i386]: PR/39356 name collision of __chkstk
References: <OF76606C74.B1B8BC85-ONC125757E.004E57F4-C125757E.004F21AB@onevision.de>

Hi Kai,

Kai Tietz wrote:

2009-03-19 Kai Tietz <kai.tietz@onevision.com>

        * config/i386/i386.md (allocate_stack_worker_32): Use
        ___gnu_chkstk.
        (allocate_stack_worker_64): Likewise.
        * config/i386/cygwin.asm  (___chkstk): Rename this
        symbol for 64-bit to ___gnu_chkstk and add it for 32-bit
        as alias for ___chkstk.

Can you clarify that the end result of this results in link compatibility with MSVC on x86_64, including MSVC code that emits _*chkstk calls?

My understanding is that the VC chkstk does not do as much stuff as GCC needs the probe to do, so you're making a new one, and it was just a mistake that it happened to be named the same thing as the MSVC one. Is this correct?

(I have no opinion on this issue otherwise. I'm just trying to understand whats going on.)

Follow-Ups:
- Re: [patch i386]: PR/39356 name collision of __chkstk
  - From: Kai Tietz

References:
- [patch i386]: PR/39356 name collision of __chkstk
  - From: Kai Tietz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]