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 driver/47480] GCC driver names a resolution file after the last argument to the linker


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

--- Comment #2 from Dmitry Gorbachev <d.g.gorbachev at gmail dot com> 2011-01-30 09:22:15 UTC ---
> So, please double-check your GCC version and paste -v output.

Checked recent weekly snapshot:

$ i686-pc-linux-gnu-gcc-4.6.0 -v
Using built-in specs.
COLLECT_GCC=i686-pc-linux-gnu-gcc-4.6.0
COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/i686-pc-linux-gnu/4.6.0/lto-wrapper
Target: i686-pc-linux-gnu
Configured with: ../gcc-4.6/configure --enable-languages=c,c++
--enable-version-specific-runtime-libs --enable-checking=yes,fold --disable-nls
--disable-shared --disable-bootstrap
Thread model: posix
gcc version 4.6.0 20110129 (experimental) (GCC) 

The bug is still here.

> I thought I improved the situation with
> +	if (infiles[i].incompiler

In this case, there are no files to compile.

> maybe we should just disregard "infiles" with starting '-' here
> (same with -Xlinker).

For example, it will not work with

$ gcc -flto -Wl,--whole-archive,-lfoobar,--no-whole-archive -save-temps

But it's probably something uncommon.


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