public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "developer at sandoe-acoustics dot co dot uk" <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 11:38:00 -0000 [thread overview]
Message-ID: <20091209113746.7609.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42333-578@http.gcc.gnu.org/bugzilla/>
------- Comment #20 from developer at sandoe-acoustics dot co dot uk 2009-12-09 11:37 -------
(In reply to comment #17)
> (In reply to comment #15)
> > (In reply to comment #13)
> > > You can try filing a bug report at Apple, but I think a better route would be
> > > to see if we can avoid linking in the system ___divdc3 from FSF GCC.
Summary (for Dominique's test case):
working [regardless of placement of -lm]:
Darwin 9 [ppc/i686]
Apple 4.0,4.2
FSF 4.5
Darwin 10
Apple 4.0, 4.2
FSF 4.5 without -lm
FSF 4.5 fails with the placement of -lm (which causes linkage of
/usr/lib/libSystem version of ___divdc3)
the latter can be emulated using Apple's 4.2 by compiling the asm output from
FSF 4.5 for Dominique's test case.
So; Apple's two compilers that produce in-line code for ___divdc3 are
apparently 'doing the right thing' (in spite of your concern about potential
optimization issues). We might look at porting the relevant .md sections to
FSF ...
The regression is in the library version of ___divdc3 supplied in Darwin10
(i.e. nothing to do with FSF gcc); This could be radared (although as you say
there is not much motivation to fix something that is unused).
I repeat my earlier question:
Why is -lm being used for this test case?
Darwin, AFAIR, does not use -lm . { see comment in gcc/config/darwin.h #define
MATH_LIBRARY "" }
(of course, one could argue that it should be harmless, in an ideal world)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42333
next prev parent reply other threads:[~2009-12-09 11:38 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 [this message]
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
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=20091209113746.7609.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).