public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: pme@gcc.gnu.org To: cheng@pcigeomatics.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: c++/5667: Internal compiler error Date: Fri, 19 Apr 2002 13:53:00 -0000 [thread overview] Message-ID: <20020419205341.6749.qmail@sources.redhat.com> (raw) Synopsis: Internal compiler error State-Changed-From-To: open->closed State-Changed-By: pme State-Changed-When: Fri Apr 19 13:53:35 2002 State-Changed-Why: Thank you for your bug report. Using 3.1 prerelease sources, I get lots of errors, but no crash at the end, so this appers fixed: 232% g++ 5667_vecclean.ii In file included from vecclean.cpp:84: ../../../lib/pcl.hh:100: `operator new' takes type `size_t' (`unsigned int') as first parameter In file included from /usr/local/include/g++-v3/bits/stl_algobase.h:75, from /usr/local/include/g++-v3/bits/std_list.h:61, from /usr/local/include/g++-v3/list:31, from stlincl.h:43, from vecclean.cpp:86: /usr/local/include/g++-v3/new:76: `operator new' takes type `size_t' (`unsigned int') as first parameter /usr/local/include/g++-v3/new:77: `operator new' takes type `size_t' (`unsigned int') as first parameter /usr/local/include/g++-v3/new:80: `operator new' takes type `size_t' (`unsigned int') as first parameter /usr/local/include/g++-v3/new:81: `operator new' takes type `size_t' (`unsigned int') as first parameter /usr/local/include/g++-v3/new:86: `operator new' takes type `size_t' (`unsigned int') as first parameter /usr/local/include/g++-v3/new:87: `operator new' takes type `size_t' (`unsigned int') as first parameter In file included from /usr/local/include/g++-v3/bits/std_list.h:61, from /usr/local/include/g++-v3/list:31, from stlincl.h:43, from vecclean.cpp:86: /usr/local/include/g++-v3/bits/stl_algobase.h: In function `void std::fill(unsigned char*, unsigned char*, const unsigned char&)': /usr/local/include/g++-v3/bits/stl_algobase.h:479: call of overloaded `memset( unsigned char*&, unsigned char&, int)' is ambiguous <internal>:479: candidates are: void* std::memset(void*, int, unsigned int) /usr/include/string.h:69: void* memset(void*, int, long unsigned int) /usr/local/include/g++-v3/bits/stl_algobase.h: In function `void std::fill(signed char*, signed char*, const signed char&)': /usr/local/include/g++-v3/bits/stl_algobase.h:486: call of overloaded `memset( signed char*&, unsigned char&, int)' is ambiguous <internal>:486: candidates are: void* std::memset(void*, int, unsigned int) /usr/include/string.h:69: void* memset(void*, int, long unsigned int) /usr/local/include/g++-v3/bits/stl_algobase.h: In function `void std::fill(char*, char*, const char&)': /usr/local/include/g++-v3/bits/stl_algobase.h:492: call of overloaded `memset( char*&, unsigned char&, int)' is ambiguous <internal>:492: candidates are: void* std::memset(void*, int, unsigned int) /usr/include/string.h:69: void* memset(void*, int, long unsigned int) /usr/local/include/g++-v3/bits/stl_algobase.h: In function `int std::__lexicographical_compare_3way(const unsigned char*, const unsigned char*, const unsigned char*, const unsigned char*)': /usr/local/include/g++-v3/bits/stl_algobase.h:691: call of overloaded `memcmp( const unsigned char*&, const unsigned char*&, const long int&)' is ambiguous <internal>:691: candidates are: int std::memcmp(const <anonymous>*, const <anonymous>*, unsigned int) /usr/include/string.h:51: int memcmp(const void*, const void*, long unsigned int) 233% http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5667
next reply other threads:[~2002-04-19 20:53 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-19 13:53 pme [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-02-12 6:56 cheng
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=20020419205341.6749.qmail@sources.redhat.com \ --to=pme@gcc.gnu.org \ --cc=cheng@pcigeomatics.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --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).