public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/40532] FAIL: gcc.dg/builtins-65.c (test for excess errors)
Date: Thu, 25 Jun 2009 07:26:00 -0000 [thread overview]
Message-ID: <20090625072606.25493.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40532-276@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from ubizjak at gmail dot com 2009-06-25 07:26 -------
(In reply to comment #2)
> > Can you put HAVE_C99_RUNTIME around problematic conversions (just copy the
> > approach from builtins-18.c) ?
>
> Attached diff. However, there's still a call left to linK_error.
This is due to the fact that your libm provides logb and ilogb.
However, according to linux mapages, these are C99 functions. Your target
doesn't define TARGET_C99_FUNCTIONS, so optimizer does not recognize logb and
ilogb as functions that can be converted.
I will simply disable builtins-65.c for non-C99 targets
--
ubizjak at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot gnu |ubizjak at gmail dot com
|dot org |
Status|UNCONFIRMED |ASSIGNED
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2009-06-25 07:26:05
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40532
next prev parent reply other threads:[~2009-06-25 7:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 1:10 [Bug testsuite/40532] New: " danglin at gcc dot gnu dot org
2009-06-24 6:35 ` [Bug testsuite/40532] " ubizjak at gmail dot com
2009-06-25 0:32 ` dave at hiauly1 dot hia dot nrc dot ca
2009-06-25 7:26 ` ubizjak at gmail dot com [this message]
2009-06-25 7:34 ` ubizjak at gmail dot com
2009-06-26 9:02 ` uros at gcc dot gnu dot org
2009-06-26 9:04 ` ubizjak at gmail dot com
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=20090625072606.25493.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).