This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
RE: [PATCH] [PATCH] Report LTO phase in lto1 process name v2
- From: <green at moxielogic dot com>
- To: "Andi Kleen" <andi at firstfloor dot org>
- Cc: rmansfield at qnx dot com, gcc-patches at gcc dot gnu dot org, ak at linux dot intel dot com, "DJ Delorie" <dj at redhat dot com>
- Date: Thu, 18 Nov 2010 14:12:12 -0700
- Subject: RE: [PATCH] [PATCH] Report LTO phase in lto1 process name v2
Andi,
You shouldn't be using link tests universally in libiberty either. Many
newlib based targets can't build executables at this point in the
toolchain build.
If you look earlier in configure.ac you'll see...
# We are being configured as a target library. AC_REPLACE_FUNCS
# may not work correctly, because the compiler may not be able to
# link executables. Note that we may still be being configured
# native.
At a minimum you should wrap all this with a test for with_newlib = no.
The moxie-elf toolchain doesn't build right now because of this.
Thanks,
AG
(sorry for the top-posting. I'm temporarily using a broken client)
-------- Original Message --------
Subject: Re: [PATCH] [PATCH] Report LTO phase in lto1 process name v2
From: Andi Kleen <andi@firstfloor.org>
Date: Thu, October 07, 2010 2:32 am
To: DJ Delorie <dj@redhat.com>
Cc: rmansfield@qnx.com, gcc-patches@gcc.gnu.org, ak@linux.intel.com
Andi Kleen <andi@firstfloor.org> writes:
>
> Subject: [PATCH] Turn PR_SET_NAME check into link check
>
> Fixes cross compilation for libiberty after my change
Committed as obvious now.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.