From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29484 invoked by alias); 17 Jan 2010 05:47:34 -0000 Received: (qmail 29462 invoked by uid 48); 17 Jan 2010 05:47:24 -0000 Date: Sun, 17 Jan 2010 05:47:00 -0000 Message-ID: <20100117054724.29461.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug driver/42690] Undefined reference errors with -flto -fuse-linker-plugin In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "espindola at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-01/txt/msg02023.txt.bz2 ------- Comment #14 from espindola at gcc dot gnu dot org 2010-01-17 05:47 ------- I don't think that in general we can support things like -nodefaultlibs -lc -lgcc. Doing that with static libraries and lto is such an uncommon case that it is probably OK to ask the user to also pass -Wl,-pass-through... I am not familiar with the driver code, but if we already have SPEC stings that are used only when linking libgcc or libc, that is the perfect place to add %{fuse-linker-plugin: -plugin-opt=-pass-through=...} -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42690