public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/45702] [4.6 Regression] New LTO test failures
Date: Mon, 20 Sep 2010 16:56:00 -0000 [thread overview]
Message-ID: <20100920165628.26381.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45702-682@http.gcc.gnu.org/bugzilla/>
------- Comment #13 from hjl dot tools at gmail dot com 2010-09-20 16:56 -------
Here is the deal:
1. The linker default search paths are /lib, /usr/lib.
2. "ld -r" disables the linker default search paths.
3. Gcc always passes -Lmulti-lib-dir to ld when multi-lib is enabled.
On Linux/ia32, gcc never passes -L/lib -L/usr/lib to linker. It
works with the linker default search paths. But "gcc -r" disables
the linker default search paths and "gcc -r -lm" doesn't work.
On Linux/x86-64, gcc always passes -Lmulti-lib-dir to linker
and "gcc -r -lm" works with -m32/-m64.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45702
next prev parent reply other threads:[~2010-09-20 16:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 12:43 [Bug lto/45702] New: [4.6 Regression] New " hjl dot tools at gmail dot com
2010-09-17 12:57 ` [Bug lto/45702] [4.6 Regression] New LTO " rguenther at suse dot de
2010-09-17 13:35 ` hjl dot tools at gmail dot com
2010-09-17 13:36 ` hjl dot tools at gmail dot com
2010-09-17 13:48 ` rguenther at suse dot de
2010-09-17 13:52 ` hjl dot tools at gmail dot com
2010-09-17 13:58 ` rguenther at suse dot de
2010-09-17 13:58 ` jakub at gcc dot gnu dot org
2010-09-17 14:04 ` jakub at gcc dot gnu dot org
2010-09-17 14:07 ` rguenther at suse dot de
2010-09-17 14:08 ` hjl dot tools at gmail dot com
2010-09-17 14:11 ` hjl dot tools at gmail dot com
2010-09-17 14:14 ` rguenther at suse dot de
2010-09-20 16:56 ` hjl dot tools at gmail dot com [this message]
2010-09-20 17:10 ` hjl dot tools at gmail dot com
2010-09-21 0:44 ` danglin at gcc dot gnu dot org
2010-09-21 8:44 ` rguenther at suse dot de
2010-09-21 20:40 ` dave at hiauly1 dot hia dot nrc dot ca
[not found] <bug-45702-4@http.gcc.gnu.org/bugzilla/>
2010-09-27 19:35 ` ro at gcc dot gnu.org
2010-09-29 19:02 ` rguenth at gcc dot gnu.org
2010-09-30 17:41 ` rguenth at gcc dot gnu.org
2010-10-04 0:41 ` danglin at gcc dot gnu.org
2010-10-04 8:51 ` rguenther at suse dot de
2010-10-26 1:09 ` jakub at gcc dot gnu.org
2010-11-04 11:10 ` rguenth at gcc dot gnu.org
2010-11-04 11:11 ` rguenth at gcc dot gnu.org
2010-11-23 23:57 ` danglin at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100920165628.26381.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).