public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gseanmcg at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/47981] gcc.dg/lto/20110201-1 FAILs on Solaris 10
Date: Mon, 07 Mar 2011 20:08:00 -0000	[thread overview]
Message-ID: <bug-47981-4-NSSXsTagOS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47981-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47981

--- Comment #3 from Sean McGovern <gseanmcg at gmail dot com> 2011-03-07 20:08:00 UTC ---
changing the cabs() call to __builtin_cabs() does succeed.


  parent reply	other threads:[~2011-03-07 20:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-04  0:48 [Bug lto/47981] New: " gseanmcg at gmail dot com
2011-03-04 10:43 ` [Bug lto/47981] " rguenth at gcc dot gnu.org
2011-03-04 13:37 ` gseanmcg at gmail dot com
2011-03-07 20:08 ` gseanmcg at gmail dot com [this message]
2011-03-08  7:34 ` ebotcazou 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=bug-47981-4-NSSXsTagOS@http.gcc.gnu.org/bugzilla/ \
    --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).