public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: mgoodman@csua.berkeley.edu To: gcc-gnats@gcc.gnu.org Subject: c++/10468: Type interpreted as int& instead of const int& Date: Wed, 23 Apr 2003 20:36:00 -0000 [thread overview] Message-ID: <20030423202657.17069.qmail@sources.redhat.com> (raw) >Number: 10468 >Category: c++ >Synopsis: Type interpreted as int& instead of const int& >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: rejects-legal >Submitter-Id: net >Arrival-Date: Wed Apr 23 20:36:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: mgoodman@csua.berkeley.edu >Release: gcc version 3.4 20030423 (experimental) >Organization: >Environment: Red Hat Linux 9 >Description: gcc interprets the type of t1 as int& instead of const int& in the attached code. The error shows up in the gcc-3_2-branch as well but the message is different. The code compiles in gcc 2.95.3. >How-To-Repeat: gcc -c -o test test.ii >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="test.ii" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="test.ii" IyAxICJ0ZXN0LmNjIgojIDEgIjxidWlsdC1pbj4iCiMgMSAiPGNvbW1hbmQgbGluZT4iCiMgMSAi dGVzdC5jYyIKdGVtcGxhdGUgPGNsYXNzIFQ+CnZvaWQgdGVzdChUIHQpIHsKICBpbnQgeCA9IDA7 CiAgY29uc3QgdHlwZW9mKHgpICYgdDEgPSB4KzA7Cn0KCmludCBtYWluKGludCBhcmdjLCBjaGFy ICoqYXJndikgewogIHRlc3QoMCk7CiAgcmV0dXJuIDA7Cn0K
next reply other threads:[~2003-04-23 20:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-23 20:36 mgoodman [this message] 2003-04-23 21:47 bangerth 2003-04-30 6:26 Mark Goodman
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=20030423202657.17069.qmail@sources.redhat.com \ --to=mgoodman@csua.berkeley.edu \ --cc=gcc-gnats@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).