This is the mail archive of the gcc-bugs@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]

[Bug testsuite/48245] FAIL: gcc.dg/lto/pr46940 c_lto_pr46940_0.o assemble on *-apple-darwin*


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48245

--- Comment #3 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2011-03-23 15:05:17 UTC ---
> The linker is
>
> @(#)PROGRAM:ld  PROJECT:ld64-97.17
> llvm version 2.9svn, from Apple Clang 1.7 (build 77)
>
> on x86_64-apple-darwin10.7.0, and
>
> @(#)PROGRAM:ld  PROJECT:ld64-85.2.1
>
> on powerpc-apple-darwin9.

So both of them non-GNU and not supporting -plugin.

> In gcc/auto-host.h I have
>
> ...
> /* Define to the level of your linker's plugin support. */
> #ifndef USED_FOR_TARGET
> #define HAVE_LTO_PLUGIN 0
> #endif
> ...

As it should: vendor linker without plugin support.

> I have grepped the different *.log files, but I did not see any
>
> gcc: error: -fuse-linker-plugin is not supported in this configuration

This would only occur in gcc/testsuite/*/*.log, but of course with xgcc
or something as the command name.

What happens if you try to compile and link the test program from
check_linker_plugin_available with the new gcc?

$ cd gcc
$ cat > lpl.c
int main() { return 0; }
$ ./xgcc -B./ -flto -fuse-linker-plugin lpl.c

    Rainer


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