public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/9881: Incorrect address calculation for static class member Date: Sun, 02 Mar 2003 22:16:00 -0000 [thread overview] Message-ID: <20030302221601.3242.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/9881; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: "Peter A. Buhr" <pabuhr@plg2.math.uwaterloo.ca> Cc: asharji@uwaterloo.ca, <gcc-bugs@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org> Subject: Re: c++/9881: Incorrect address calculation for static class member Date: Sun, 2 Mar 2003 16:06:41 -0600 (CST) > It seems to me that a cast to a pointer should always have the same meaning. > That is, when reinterpreting the bits, the meaning of those bits cannot imply a > static context in one case and a dynamic in another. That seems too bizarre. This I leave to ones more trained in C++ standard legalese. > So what is the next step? My code use to work with gcc 3.2 and now fails with > gcc 3.3. My understanding is that gcc3.3 is scheduled for release very soon and > I would like my code to work with it. What law firm do I need to hire to press > my case as it seems the issue is an open question for the current version of > g++. What if I get a note from Bjarne saying which way it's suppose to go? Then this would be one more in the list of 400 or so C++ reports where we know that gcc is doing the wrong thing. If your claim is right then this would be a regression -- that would raise the priority of the report, but doesn't imply any guarantees. You didn't pay for gcc you have no claim against it. If you really need to make your code run with gcc3.3, you have 3 options: - you fix gcc - you pay someone to fix gcc - you work around it in your code. > However, the bottom-line is that I should not need to justify a legitimate use > for some feature in the language. (What a programmer wishes to do in the > privacy their own code is their business.) The feature is there for me to use, > and should work correctly (modulo the current outstanding legal question). True enough, modulo the thing about free software: it comes "as is", without any guarantees. Sorry for not being of more help Wolfgang ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth/
next reply other threads:[~2003-03-02 22:16 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-02 22:16 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-28 13:56 Peter A. Buhr 2003-02-27 23:16 Wolfgang Bangerth 2003-02-27 22:56 Peter A. Buhr 2003-02-27 22:06 Wolfgang Bangerth 2003-02-27 21:46 Peter A. Buhr 2003-02-27 21:40 bangerth 2003-02-27 18:22 bangerth 2003-02-27 18:06 asharji
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=20030302221601.3242.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --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).