public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/57047] [4.7/4.8/4.9 Regression] [C++11] stl_pair.h:137:64: internal compiler error: Segmentation fault in constexpr constructor Date: Tue, 23 Apr 2013 15:10:00 -0000 [thread overview] Message-ID: <bug-57047-4-x3gOMVmwBa@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57047-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57047 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jason at gcc dot gnu.org Target Milestone|--- |4.7.4 Summary|[C++11] stl_pair.h:137:64: |[4.7/4.8/4.9 Regression] |internal compiler error: |[C++11] stl_pair.h:137:64: |Segmentation fault in |internal compiler error: |constexpr constructor |Segmentation fault in | |constexpr constructor --- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-04-23 15:10:32 UTC --- Reduced testcase: template <typename> struct A; template <typename T> struct A <T &> { typedef T type; }; template <typename T> constexpr T && foo (typename A <T>::type & __t) noexcept { return static_cast <T &&>(__t); } template <class T1, class T2> struct B { T1 t1; T2 t2; template <class U> constexpr B (U && __x, const T2 & __y) : t1 (foo <U> (__x)), t2 (__y) {} }; static inline constexpr bool fn1 (const char c) { return ('0' <= c) && (c <= '9'); } static inline constexpr bool fn2 (const char c) { return (('A' <= c) && (c <= 'Z')) || (('a' <= c) && (c <= 'z')); } static constexpr bool fn3 (const char *const x) { return (x[1] == '\0' && x[0] == ']') ? true : (!fn1 (x[0])) ? false : fn3 (&x[1]); } static constexpr bool fn4 (const char *const x) { return (x[0] == '\0') ? fn3 (&x[1]) : fn4 (&x[1]); } static inline constexpr bool fn5 (const char *const x) { return fn2 (x[0]) ? fn4 (x) : false; } struct C final { constexpr C (const char *const t1) : c (fn5 (t1) ? 199 : 69) {} unsigned c; }; B <C, C> p ("a", "b"); Started to ICE in between r175000 and r175062.
next prev parent reply other threads:[~2013-04-23 15:10 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-23 12:49 [Bug libstdc++/57047] New: " mattyclarkson at gmail dot com 2013-04-23 13:19 ` [Bug c++/57047] " redi at gcc dot gnu.org 2013-04-23 13:22 ` jakub at gcc dot gnu.org 2013-04-23 13:26 ` redi at gcc dot gnu.org 2013-04-23 13:42 ` mattyclarkson at gmail dot com 2013-04-23 13:47 ` redi at gcc dot gnu.org 2013-04-23 13:53 ` mattyclarkson at gmail dot com 2013-04-23 14:07 ` mattyclarkson at gmail dot com 2013-04-23 14:17 ` mattyclarkson at gmail dot com 2013-04-23 15:10 ` jakub at gcc dot gnu.org [this message] 2013-05-10 14:36 ` [Bug c++/57047] [4.7/4.8/4.9 Regression] " jason 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-57047-4-x3gOMVmwBa@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: linkBe 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).