public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ian dot bolton at arm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/44328] switch/case optimization produces an invalid lookup table index
Date: Mon, 02 Aug 2010 12:24:00 -0000 [thread overview]
Message-ID: <20100802122343.5219.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44328-19252@http.gcc.gnu.org/bugzilla/>
------- Comment #24 from ian dot bolton at arm dot com 2010-08-02 12:23 -------
(In reply to comment #23)
> I can confirm this fails with GCC 4.4.4 and that GCC 4.3.2 works.
>
I get no warning and correct code in latest 4.4 branch (4.4.5 - 20100727), but
I do get the warning and incorrect code in latest 4.5 branch (4.5.1 -
20100727).
--
ian dot bolton at arm dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ian dot bolton at arm dot
| |com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44328
next prev parent reply other threads:[~2010-08-02 12:24 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-30 0:00 [Bug c++/44328] New: switch/case optimization produces an invalid jump " eblot dot ml at gmail dot com
2010-05-30 10:36 ` [Bug c++/44328] " eblot dot ml at gmail dot com
2010-05-30 14:50 ` mikpe at it dot uu dot se
2010-05-30 17:36 ` eblot dot ml at gmail dot com
2010-06-04 23:41 ` [Bug c++/44328] switch/case optimization produces an invalid lookup " eblot dot ml at gmail dot com
2010-06-15 15:09 ` jamborm at gcc dot gnu dot org
2010-06-17 9:21 ` eblot dot ml at gmail dot com
2010-06-17 9:37 ` Andrew Pinski
2010-06-17 9:34 ` eblot dot ml at gmail dot com
2010-06-17 9:37 ` pinskia at gmail dot com
2010-06-17 14:02 ` jamborm at gcc dot gnu dot org
2010-06-17 15:01 ` jamborm at gcc dot gnu dot org
2010-06-17 16:34 ` eblot dot ml at gmail dot com
2010-06-17 16:37 ` jamborm at gcc dot gnu dot org
2010-06-17 16:41 ` eblot dot ml at gmail dot com
2010-06-20 13:53 ` eblot dot ml at gmail dot com
2010-06-20 16:51 ` jamborm at gcc dot gnu dot org
2010-06-20 16:57 ` eblot dot ml at gmail dot com
2010-06-20 17:03 ` eblot dot ml at gmail dot com
2010-06-20 18:26 ` mikpe at it dot uu dot se
2010-06-21 8:29 ` jamborm at gcc dot gnu dot org
2010-06-21 10:45 ` mikpe at it dot uu dot se
2010-06-21 11:18 ` mikpe at it dot uu dot se
2010-07-05 13:43 ` [Bug tree-optimization/44328] " ramana at gcc dot gnu dot org
2010-07-24 22:24 ` jifl-bugzilla at jifvik dot org
2010-08-02 12:24 ` ian dot bolton at arm dot com [this message]
2010-08-02 13:33 ` ian dot bolton at arm dot com
2010-08-03 17:09 ` ian dot bolton at arm dot com
2010-09-01 11:10 ` jamborm at gcc dot gnu dot org
2010-09-01 11:23 ` jamborm at gcc dot gnu dot org
2010-09-01 11:24 ` jamborm at gcc dot gnu dot org
2010-09-01 11:25 ` ibolton at gcc dot gnu dot org
2010-09-01 11:33 ` jamborm at gcc dot gnu dot org
2010-09-01 11:47 ` jifl-bugzilla at jifvik dot org
2010-09-01 11:50 ` jakub at gcc dot gnu dot org
2010-09-02 13:10 ` ibolton at gcc dot gnu dot org
2010-09-07 9:28 ` ibolton at gcc dot gnu dot org
2010-09-09 15:37 ` ibolton at gcc dot gnu dot org
2010-09-09 15:38 ` rguenth at gcc dot gnu 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=20100802122343.5219.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).