public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "peter.sommerlad at hsr dot ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/54413] Option for turning off compiler extensions for -std=c++11 with respect to complex/fixed-point numbers missing
Date: Mon, 15 Oct 2012 21:17:00 -0000	[thread overview]
Message-ID: <bug-54413-4-ObxEk0358E@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54413-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #7 from Peter Sommerlad <peter.sommerlad at hsr dot ch> 2012-10-15 21:17:07 UTC ---
(In reply to comment #6)
> So what should these flags look like?
> 
> -fno-complex-literals
> -fno-fixed-literals
looks fine in principle.
> 
> Or should I use -W?
> 
> Should -std=c++11, etc. set these by default 
> (and you turn then back on with -fcomplex-literals, -ffixed-literals?)

I would happy with -ansi -std=c++11 work as I expected.

turning the extensions off with just -std=c++11 would not be what you want,
since existing code might rely on these extensions, only when we get -std=c++16
with my paper on UDL accepted, we should turn off these extensions, because
then the standard library will ship with the UDL suffixes identical or closely
to the GNU extensions.


  parent reply	other threads:[~2012-10-15 21:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-30  8:19 [Bug c++/54413] New: " p4spam at hispeed dot ch
2012-08-30  9:11 ` [Bug c++/54413] " jakub at gcc dot gnu.org
2012-08-30  9:55 ` redi at gcc dot gnu.org
2012-08-30 10:04 ` jakub at gcc dot gnu.org
2012-10-01 16:52 ` paolo.carlini at oracle dot com
2012-10-01 18:47 ` 3dw4rd at verizon dot net
2012-10-15 21:08 ` 3dw4rd at verizon dot net
2012-10-15 21:17 ` peter.sommerlad at hsr dot ch [this message]
2012-10-15 21:19 ` redi at gcc dot gnu.org
2012-10-15 21:21 ` peter.sommerlad at hsr dot ch
2012-10-15 21:25 ` 3dw4rd at verizon dot net
2012-11-05  4:50 ` 3dw4rd at verizon dot net
2012-11-05  4:56 ` 3dw4rd at verizon dot net
2012-11-06 17:55 ` 3dw4rd at verizon dot net
2012-11-12  5:39 ` 3dw4rd at verizon dot net
2012-11-12  9:12 ` redi at gcc dot gnu.org
2012-11-12 17:48 ` 3dw4rd at verizon dot net
2012-11-12 18:30 ` redi at gcc dot gnu.org
2012-11-14 13:07 ` 3dw4rd at verizon dot net
2012-11-14 13:18 ` paolo.carlini at oracle dot com
2012-11-14 13:21 ` 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-54413-4-ObxEk0358E@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).