public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/32023] No casts in lvalue error message
Date: Tue, 22 May 2007 23:27:00 -0000	[thread overview]
Message-ID: <20070522232727.7600.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32023-14066@http.gcc.gnu.org/bugzilla/>



------- Comment #9 from pinskia at gcc dot gnu dot org  2007-05-23 00:27 -------
(In reply to comment #8)
> gcc dropped a lot of features which weren't included in standard recently and
> thus many of us wondering why the code which compiled before doesn't compile
> now. It's fine for me to have strict compiler but it's also useful to get at
> least an idea what compiler doesn't like without reading whole standard.

And that is exactly why GCC has changes page to describe these changes.  Yes
this specific change is documented on that page.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32023


  parent reply	other threads:[~2007-05-22 23:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-21 14:29 [Bug c/32023] New: Invalid lvalue in void* increment error inconsitensy nshmyrev at yandex dot ru
2007-05-21 14:45 ` [Bug c/32023] " schwab at suse dot de
2007-05-22 17:16 ` [Bug c/32023] No casts in lvalue error message nshmyrev at yandex dot ru
2007-05-22 17:27 ` pinskia at gcc dot gnu dot org
2007-05-22 17:33 ` nshmyrev at yandex dot ru
2007-05-22 20:33 ` schwab at suse dot de
2007-05-22 20:36 ` nshmyrev at yandex dot ru
2007-05-22 20:51 ` schwab at suse dot de
2007-05-22 23:13 ` nshmyrev at yandex dot ru
2007-05-22 23:27 ` pinskia at gcc dot gnu dot org [this message]
2007-05-23 15:57 ` manu at gcc dot gnu dot org
2007-05-23 16:06 ` nshmyrev at yandex dot ru

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=20070522232727.7600.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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: link
Be 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).