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/17253] Inconsistency in reading array indexes Date: Tue, 31 Aug 2004 20:44:00 -0000 [thread overview] Message-ID: <20040831204432.22629.qmail@sourceware.org> (raw) In-Reply-To: <20040831195044.17253.vanveghel@home.nl> ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-08-31 20:44 ------- No there is nothing which can be improved except maybe for you fixing your code not be use undefined code. -- What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17253
next prev parent reply other threads:[~2004-08-31 20:44 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-08-31 19:50 [Bug c/17253] New: " vanveghel at home dot nl 2004-08-31 20:03 ` [Bug c/17253] " falk at debian dot org 2004-08-31 20:44 ` pinskia at gcc dot gnu dot org [this message] 2004-08-31 20:46 ` bangerth at dealii dot org 2004-08-31 20:46 ` bangerth at dealii dot 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=20040831204432.22629.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: 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).