public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <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 09:32:00 -0000 [thread overview]
Message-ID: <20091209093142.22322.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42333-578@http.gcc.gnu.org/bugzilla/>
------- Comment #19 from dominiq at lps dot ens dot fr 2009-12-09 09:31 -------
> As far as generation of a test case is concerned - why not just use the asm
> generated by 4.5?
I did that and the assembly generated on darwin10 works fine on darwin9. I can
fill a bug report to Apple to know if its a bug (regression) or a feature.
> On what to do about builtin-math-7.c testcase, my inclination is we should just
> XFAIL it for darwin10 since fixing darwin's ___divdc3 won't help with
> distributions out in the field.
For the moment I'll prefer to keep the failure until the use of -lm in the
testsuite is clarified:
My understanding of the testsuite is that it is supposed to check that the gcc
compilers are working as expected on a given target. Does it make any sense to
pass the tests with -lm when it is not used in normal use of the compilers? If
yes, why? If no, what must be changed in gcc to run the testsuite (at least on
Darwin) without adding -lm to the tests? (see also related questions in
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41473#c87).
I am planning to ask these question in the gcc list, but I won't have much time
to do it before this evening, so if someone want to beat me for it, he is
welcome!
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42333
next prev parent reply other threads:[~2009-12-09 9:32 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 [this message]
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
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=20091209093142.22322.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).