public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "p4spam at hispeed dot ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/54413] New: Option for turning off compiler extensions for -std=c++11 with respect to complex/fixed-point numbers missing
Date: Thu, 30 Aug 2012 08:19:00 -0000 [thread overview]
Message-ID: <bug-54413-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54413
Bug #: 54413
Summary: Option for turning off compiler extensions for
-std=c++11 with respect to complex/fixed-point numbers
missing
Classification: Unclassified
Product: gcc
Version: 4.7.1
Status: UNCONFIRMED
Severity: major
Priority: P3
Component: c++
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: p4spam@hispeed.ch
All versions of g++ that support UDL operators should have such an option to
turn off GNU complex literals and fixed point literals extensions.
I am prototyping C++1x library extensions for user-defined literals. While it
is possible to turn off GCC's extensions for complex numbers for "old" C++ it
is impossible to combine the effects of -ansi with -std=c++11. Especially the
syntax extensions for complex numbers, e.g., 1.1i cannot be turned off and thus
do not allow testing of UDL operators for the purpose of creating
std::complex<> literals, such as
constexpr std::complex<double> operator"" i(long double d){
return std::complex<double>(0,d);
}
>From the fixed-point extension also number suffixes r and R are occupied.
More info at my proposal,
http://wiki.hsr.ch/PeterSommerlad/files/N3402_UDLsuffixes.pdf
All versions of g++ that support UDL operators should have such an option to
turn off GNU complex literals and fixed point literals extensions.
next reply other threads:[~2012-08-30 8:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 8:19 p4spam at hispeed dot ch [this message]
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
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@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).