public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: arnez@de.ibm.com To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/7884: code compiled with optimization flag causes segmentation violation Date: Thu, 12 Sep 2002 01:46:00 -0000 [thread overview] Message-ID: <20020912084606.8183.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/7884; it has been noted by GNATS. From: arnez@de.ibm.com To: aloeff@de.ibm.com, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: c++/7884: code compiled with optimization flag causes segmentation violation Date: Thu, 12 Sep 2002 10:44:10 +0200 I don't quite understand why (char *)foo is an rvalue. Using a cast as an lvalue is listed as one of GCC's extensions. In particular GCC allows me to write: extern int do_stuff(void *bar); int f(char *str) { void *foo; (char *) foo = str+1; return do_stuff(foo); } I can compile this both in C or C++ mode, even with -ansi and -pedantic. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7884
next reply other threads:[~2002-09-12 8:46 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-09-12 1:46 arnez [this message] 2002-09-12 4:16 Gabriel Dos Reis 2002-09-12 5:36 Gabriel Dos Reis
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=20020912084606.8183.qmail@sources.redhat.com \ --to=arnez@de.ibm.com \ --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).