public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Giovanni Bajo" <giovannibajo@libero.it> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/10079: With two identical template function signatures gcc crashes instead of emitting "ambiguous" or "duplicate" Date: Fri, 02 May 2003 19:06:00 -0000 [thread overview] Message-ID: <20030502190601.31165.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/10079; it has been noted by GNATS. From: "Giovanni Bajo" <giovannibajo@libero.it> To: <gcc-gnats@gcc.gnu.org>, <stip@mathematik.uni-ulm.de>, <gcc-bugs@gcc.gnu.org>, <nobody@gcc.gnu.org>, <gcc-prs@gcc.gnu.org> Cc: Subject: Re: c++/10079: With two identical template function signatures gcc crashes instead of emitting "ambiguous" or "duplicate" Date: Fri, 2 May 2003 20:58:00 +0200 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10079 Very weird. I can't compress it more than this: ---------------------------------------------------------- template <bool> struct Foo {}; template <typename> struct Bar {}; template <typename> struct true_t { enum { value = true }; }; template <typename T, typename U> Foo<(true_t<T>::value && true_t<T>::value)> func(T t, U u) {} template <typename T, typename U> void func(Bar<T>, Bar<U> ) {} int main() { Bar<void> v; func(v, v); } ---------------------------------------------------------- pr10079.cpp: In function `int main()': pr10079.cpp:30: internal compiler error: Segmentation fault Please submit a full bug report, In my wild guess, the segfault happens while trying to format the error message about the ambiguity of the call, which requires printing the declaration of the first func<> (that is quite complex). Reconfirmed on everything (2.95 -> 3.4 CVS 20030430). Giovanni Bajo
next reply other threads:[~2003-05-02 19:06 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-02 19:06 Giovanni Bajo [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-17 10:15 ehrhardt 2003-03-14 15:15 bangerth 2003-03-14 11:36 stip
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=20030502190601.31165.qmail@sources.redhat.com \ --to=giovannibajo@libero.it \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).