On Wed, Jan 22, 2014 at 10:16 AM, Matthias Klose wrote:
>
> Ok, but I cannot do this directly. gcc_cv_ld may already be an absolute path.
> So now I'm checking the very same location as gcc_cv_ld first, then fall back
> to
> AC_PATH_PROG.
When I look at gcc/configure.ac and gcc/exec-tool.in, it
On Wed, Jan 22, 2014 at 10:16 AM, Matthias Klose wrote:
> Am 18.01.2014 03:03, schrieb Ian Lance Taylor:
>> On Fri, Nov 29, 2013 at 5:29 AM, Matthias Klose wrote:
>>> to get full advantage of the -fsplit-stack option, gccgo binaries have to be
>>> linked with gold, not the bfd linker. When the s
Am 18.01.2014 03:03, schrieb Ian Lance Taylor:
> On Fri, Nov 29, 2013 at 5:29 AM, Matthias Klose wrote:
>> to get full advantage of the -fsplit-stack option, gccgo binaries have to be
>> linked with gold, not the bfd linker. When the system linker defaults to the
>> bfd linker, then gccgo should
On Fri, Nov 29, 2013 at 5:29 AM, Matthias Klose wrote:
> to get full advantage of the -fsplit-stack option, gccgo binaries have to be
> linked with gold, not the bfd linker. When the system linker defaults to the
> bfd linker, then gccgo should explicitly use the gold linker, passing
> fuse-ld=go
ping patch
Am 29.11.2013 14:29, schrieb Matthias Klose:
> to get full advantage of the -fsplit-stack option, gccgo binaries have to be
> linked with gold, not the bfd linker. When the system linker defaults to the
> bfd linker, then gccgo should explicitly use the gold linker, passing
> fuse-ld=g
to get full advantage of the -fsplit-stack option, gccgo binaries have to be
linked with gold, not the bfd linker. When the system linker defaults to the
bfd linker, then gccgo should explicitly use the gold linker, passing
fuse-ld=gold, unless another -fuse-ld option is present. Tested with and
