public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Peter Schmid <schmid@snake.iap.physik.tu-darmstadt.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/7858: g++ rejects legal code (regression from gcc 3.*) Date: Sun, 08 Sep 2002 16:06:00 -0000 [thread overview] Message-ID: <20020908230601.1632.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/7858; it has been noted by GNATS. From: Peter Schmid <schmid@snake.iap.physik.tu-darmstadt.de> To: Andrew Pinski <pinskia@physics.uc.edu> Cc: <gcc-gnats@gcc.gnu.org>, <bkoz@redhat.com> Subject: Re: c++/7858: g++ rejects legal code (regression from gcc 3.*) Date: Mon, 9 Sep 2002 00:58:03 +0200 (CEST) Dear Andrew Pinski, If you argument is true then the code in the header file bits/stl_function.h has to be corrected since the binder1st facility included in this PR is copied from this file. I do not understand the error message "error: non-lvalue in unary `&'". Could you please explain why the compiler emits this message? Furthermore, since about a week or so STLport does not compile. The file ../lib/obj/GCC-LINUX/ReleaseD/dll_main.cpp is rejected by the compiler with a "./stlport/stl/_string.h:773: error: non-lvalue in unary `&'" message. There are similar problems with boost. I extracted the testcase included in this PR from boost/libs/utility/indirect_iterator_example.cpp. Thanks, Peter Schmid
next reply other threads:[~2002-09-08 23:06 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-09-08 16:06 Peter Schmid [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-09 15:34 ljrittle 2002-10-08 16:46 Pop Sébastian 2002-09-13 9:37 nathan 2002-09-09 13:26 Andrew Pinski 2002-09-09 12:56 Peter Schmid 2002-09-09 12:36 Paolo Carlini 2002-09-08 16:26 Andrew Pinski 2002-09-08 12:06 Andrew Pinski 2002-09-08 11:46 Peter Schmid
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=20020908230601.1632.qmail@sources.redhat.com \ --to=schmid@snake.iap.physik.tu-darmstadt.de \ --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).