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: Define TRY_EMPTY_VM_SPACE for Linux/x32

From: Andrew Pinski <pinskia at gmail dot com>
To: Uros Bizjak <ubizjak at gmail dot com>
Cc: "H.J. Lu" <hjl dot tools at gmail dot com>, gcc-patches at gcc dot gnu dot org
Date: Wed, 4 Apr 2012 11:53:11 -0700
Subject: Re: PATCH: Define TRY_EMPTY_VM_SPACE for Linux/x32
References: <CAFULd4afnrbE0vzrBE6v24GJkjLv8hB13YzpFTvTPb=Coy5pZw@mail.gmail.com> <CAMe9rOp16L8udrJdqyR+-D3c9WjoMmkNRjsWssKr-u1DmDPrRg@mail.gmail.com> <CAFULd4aPsgy5bnkQHHZ=nmhHu6OJJLKG4JtZHPo6_FRH5cG8oQ@mail.gmail.com>

On Wed, Apr 4, 2012 at 11:50 AM, Uros Bizjak <ubizjak@gmail.com> wrote:
> Looking at how other targets implement this check, I don't think that
> this is a problem at all. This issue only shows on a non-bootstrapped
> build. A full bootstrap will use correct address.

The other place where it shows up is cross compilers but who is going
to use a 3.2 compiler with GCC 4.8 anyways?

-- Pinski

Follow-Ups:
- Re: PATCH: Define TRY_EMPTY_VM_SPACE for Linux/x32
  - From: H.J. Lu

References:
- Re: PATCH: Define TRY_EMPTY_VM_SPACE for Linux/x32
  - From: Uros Bizjak
- Re: PATCH: Define TRY_EMPTY_VM_SPACE for Linux/x32
  - From: H.J. Lu
- Re: PATCH: Define TRY_EMPTY_VM_SPACE for Linux/x32
  - From: Uros Bizjak

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