public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at nitro dot med dot uc dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/42333] complex division failure on darwin10 with -lm
Date: Wed, 09 Dec 2009 18:41:00 -0000 [thread overview]
Message-ID: <20091209184056.5586.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42333-578@http.gcc.gnu.org/bugzilla/>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]
------- Comment #26 from howarth at nitro dot med dot uc dot edu 2009-12-09 18:40 -------
I am still a bit confused about this bug. When we leave -lm out of the linkage
of builtin-math-7.exe, where does the ___divdc3 call get resolved from?
Shouldn't it be coming libSystem since that always appears first on the command
line?
http://developer.apple.com/mac/library/documentation/Porting/Conceptual/PortingUnix/compiling/compiling.html
suggests that should be the case...
The libSystem library also includes functions that you would normally expect to
find in libc and libm, RPC services, and a name resolver. Because libSystem is
automatically linked into your application, you do not need to explicitly add
it to the compiler’s link line. For your convenience, many of these libraries
exist as symbolic links to libSystem, so while explicitly linking against -lm
(for example) is not needed, it will not cause an error.
So this sounds more like an darwin linker bug.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42333
next prev parent reply other threads:[~2009-12-09 18:41 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 16:26 [Bug other/42333] New: " ghazi at gcc dot gnu dot org
2009-12-08 16:34 ` [Bug other/42333] " dominiq at lps dot ens dot fr
2009-12-08 16:47 ` ghazi at gcc dot gnu dot org
2009-12-08 18:31 ` dominiq at lps dot ens dot fr
2009-12-08 19:30 ` howarth at nitro dot med dot uc dot edu
2009-12-08 19:34 ` dominiq at lps dot ens dot fr
2009-12-08 19:59 ` howarth at nitro dot med dot uc dot edu
2009-12-08 20:24 ` ghazi at gcc dot gnu dot org
2009-12-08 20:27 ` developer at sandoe-acoustics dot co dot uk
2009-12-08 20:51 ` developer at sandoe-acoustics dot co dot uk
2009-12-08 21:29 ` dominiq at lps dot ens dot fr
2009-12-08 22:14 ` dominiq at lps dot ens dot fr
2009-12-08 23:41 ` developer at sandoe-acoustics dot co dot uk
2009-12-08 23:58 ` ghazi at gcc dot gnu dot org
2009-12-09 0:07 ` ghazi at gcc dot gnu dot org
2009-12-09 0:12 ` howarth at nitro dot med dot uc dot edu
2009-12-09 0:19 ` howarth at nitro dot med dot uc dot edu
2009-12-09 0:34 ` ghazi at gcc dot gnu dot org
2009-12-09 1:11 ` howarth at nitro dot med dot uc dot edu
2009-12-09 9:32 ` dominiq at lps dot ens dot fr
2009-12-09 11:38 ` developer at sandoe-acoustics dot co dot uk
2009-12-09 11:42 ` rguenth at gcc dot gnu dot org
2009-12-09 15:21 ` developer at sandoe-acoustics dot co dot uk
2009-12-09 16:48 ` howarth at nitro dot med dot uc dot edu
2009-12-09 17:37 ` developer at sandoe-acoustics dot co dot uk
2009-12-09 18:29 ` mrs at apple dot com
2009-12-09 18:41 ` howarth at nitro dot med dot uc dot edu [this message]
2009-12-09 18:48 ` mrs at apple dot com
2009-12-09 18:56 ` ghazi at gcc dot gnu dot org
2009-12-09 23:06 ` howarth at nitro dot med dot uc dot edu
2009-12-10 23:44 ` sabre at nondot dot org
2009-12-11 16:44 ` ghazi at gcc dot gnu dot org
2010-04-09 20:45 ` iains at gcc dot gnu dot org
2010-04-09 20:57 ` dominiq at lps dot ens dot fr
2010-04-09 21:07 ` howarth at nitro dot med dot uc dot edu
2010-04-09 22:30 ` iains at gcc dot gnu dot org
2010-04-11 10:18 ` iains at gcc dot gnu dot org
2010-04-11 13:57 ` howarth at nitro dot med dot uc dot edu
2010-04-11 14:47 ` howarth at nitro dot med dot uc dot edu
2010-04-11 15:10 ` iains at gcc dot gnu dot org
2010-04-11 15:24 ` howarth at nitro dot med dot uc dot edu
2010-04-11 15:36 ` dominiq at lps dot ens dot fr
2010-04-13 1:07 ` iains at gcc dot gnu dot org
2010-04-13 1:54 ` howarth at nitro dot med dot uc dot edu
2010-04-13 16:02 ` howarth at nitro dot med dot uc dot edu
2010-04-13 16:07 ` howarth at nitro dot med dot uc dot edu
2010-04-13 16:30 ` dominiq at lps dot ens dot fr
2010-04-13 16:48 ` howarth at nitro dot med dot uc dot edu
2010-04-13 16:52 ` iains at gcc dot gnu dot org
2010-04-13 17:00 ` howarth at nitro dot med dot uc dot edu
2010-04-14 17:39 ` iains at gcc dot gnu dot org
[not found] <bug-42333-4@http.gcc.gnu.org/bugzilla/>
2011-02-05 21:11 ` howarth at nitro dot med.uc.edu
2011-02-05 21:49 ` howarth at nitro dot med.uc.edu
2011-02-05 22:31 ` mrs at gcc dot gnu.org
2011-02-06 16:45 ` ghazi at gcc dot gnu.org
2011-02-07 20:54 ` mrs at gcc dot gnu.org
2011-02-07 20:55 ` mrs at gcc dot gnu.org
2011-02-07 21:02 ` mrs at gcc dot gnu.org
2011-06-30 16:32 ` mrs at gcc dot gnu.org
2011-06-30 16:34 ` mrs 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=20091209184056.5586.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).