public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "icicle at cg dot tuwien.ac.at" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug objc/31056] objc bogus warning when using const
Date: Mon, 22 Nov 2010 20:37:00 -0000	[thread overview]
Message-ID: <bug-31056-4-ZH7xyxK6nQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-31056-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Thomas Gamper <icicle at cg dot tuwien.ac.at> 2010-11-22 20:27:22 UTC ---
Hi Nicola,
I am sorry, but I had to remove the preprocessed source due to to copyright
reasons. OTOH it would not have been helpful, since it wasn't a distilled
testcase. Additionally, I am not working with that code base anymore, so I do
not know if the bug is still there. Usually I myself do not use 'const' in
ObjectiveC source, but that's due to lack of knowledge about it's semantics (if
there are any?). But since you are back working on the objc frontend in gcc I
will start again to file bug reports (at least in the case I encounter any).

Thanks,
Thomas


  parent reply	other threads:[~2010-11-22 20:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-31056-4@http.gcc.gnu.org/bugzilla/>
2010-11-20 14:02 ` nicola at gcc dot gnu.org
2010-11-22 19:34 ` nicola at gcc dot gnu.org
2010-11-22 20:37 ` icicle at cg dot tuwien.ac.at [this message]
2010-11-23 23:55 ` nicola at gcc dot gnu.org
2010-11-23 23:58 ` nicola at gcc dot gnu.org
2010-11-24  0:25 ` nicola at gcc dot gnu.org
2011-03-25 19:59 ` jakub at gcc dot gnu.org
2011-03-25 22:01 ` nicola at gcc dot gnu.org
2011-04-28 16:25 ` rguenth at gcc dot gnu.org

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=bug-31056-4-ZH7xyxK6nQ@http.gcc.gnu.org/bugzilla/ \
    --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).