public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dflogeras2 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/67309] Error compiling with -std=c++11 and -fsingle-precision-constant
Date: Fri, 21 Aug 2015 19:58:00 -0000	[thread overview]
Message-ID: <bug-67309-4-JKmDzCXE3F@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67309-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67309

--- Comment #3 from Dave Flogeras <dflogeras2 at gmail dot com> ---
That is what is weird to me, it definitely used to compile for me with GCC
4.7.3 and 4.8.3 (with the same build system flags).

Is there anything that is conditional when compiling GCC that maybe the Gentoo
crossdev folks have changed over time, which could mask this behaviour?  I
don't imagine they were patching those headers.  However, when I rebuild my
cross GCC 4.7.3 with crossdev, it now fails, as you've noted.

I am happy to test patchsets, and or even come up with them if you think this
is something worth delegating.  I have no experience in GCC's tree, but I can
follow orders :)


  parent reply	other threads:[~2015-08-21 19:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21 16:39 [Bug c++/67309] New: " dflogeras2 at gmail dot com
2015-08-21 18:26 ` [Bug libstdc++/67309] " redi at gcc dot gnu.org
2015-08-21 18:28 ` redi at gcc dot gnu.org
2015-08-21 19:58 ` dflogeras2 at gmail dot com [this message]
2015-08-21 20:25 ` redi at gcc dot gnu.org
2015-08-21 20:52 ` dflogeras2 at gmail dot com
2015-08-21 21:07 ` dflogeras2 at gmail dot com
2015-08-24 13:44 ` redi at gcc dot gnu.org
2015-08-24 13:49 ` redi 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-67309-4-JKmDzCXE3F@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).