[Bug java/21855] array bounds checking elimination

2015-10-20 Thread aph at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21855 Andrew Haley changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug java/21855] array bounds checking elimination

2012-01-10 Thread tromey at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21855 --- Comment #24 from Tom Tromey 2012-01-10 17:21:02 UTC --- I found my code and it turns out I never finished it. (I did write a java-specific devirtualization pass.) Here is an introductory comment that explains my plans: /* This pass implement

[Bug java/21855] array bounds checking elimination

2012-01-10 Thread tromey at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21855 --- Comment #23 from Tom Tromey 2012-01-10 17:17:50 UTC --- I thought I wrote a pass to do this optimization, but I can't find it now. Anyway I think that would be the simplest approach by far.

[Bug java/21855] array bounds checking elimination

2012-01-10 Thread aph at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21855 --- Comment #22 from Andrew Haley 2012-01-10 17:08:30 UTC --- (In reply to comment #21) > The Java frontend could handle this by performing loads of the length field > via a SAVE_EXPR and sharing this across a function. That way CSE would > happ

[Bug java/21855] array bounds checking elimination

2012-01-10 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21855 --- Comment #20 from Richard Guenther 2012-01-10 16:55:52 UTC --- (In reply to comment #19) > > > No. What you can do is, via the method I outlined, tell GCC that > > args is to be treated similar to a local automatic variable - thus > > it cann

[Bug java/21855] array bounds checking elimination

2012-01-10 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21855 --- Comment #21 from Richard Guenther 2012-01-10 16:57:36 UTC --- The Java frontend could handle this by performing loads of the length field via a SAVE_EXPR and sharing this across a function. That way CSE would happen automagically.

[Bug java/21855] array bounds checking elimination

2012-01-10 Thread aph at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21855 --- Comment #19 from Andrew Haley 2012-01-10 16:44:16 UTC --- (In reply to comment #17) > (In reply to comment #16) > > (In reply to comment #15) > > > (In reply to comment #14) > > > > (In reply to comment #13) > > > > > We can't optimize this b

[Bug java/21855] array bounds checking elimination

2012-01-10 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21855 --- Comment #18 from Richard Guenther 2012-01-10 16:35:46 UTC --- (In reply to comment #17) > (In reply to comment #16) > > (In reply to comment #15) > > > (In reply to comment #14) > > > > (In reply to comment #13) > > > > > We can't optimize th

[Bug java/21855] array bounds checking elimination

2012-01-10 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21855 --- Comment #17 from Richard Guenther 2012-01-10 16:30:30 UTC --- (In reply to comment #16) > (In reply to comment #15) > > (In reply to comment #14) > > > (In reply to comment #13) > > > > We can't optimize this because System.out.println can ch

[Bug java/21855] array bounds checking elimination

2012-01-10 Thread aph at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21855 --- Comment #16 from Andrew Haley 2012-01-10 16:26:51 UTC --- (In reply to comment #15) > (In reply to comment #14) > > (In reply to comment #13) > > > We can't optimize this because System.out.println can change args[]. > > > > That's the whole

[Bug java/21855] array bounds checking elimination

2012-01-10 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21855 Richard Guenther changed: What|Removed |Added Status|WAITING |NEW Component|tree-optimizati