[Bug rtl-optimization/37262] Two branches of the same condition being emitted

2017-11-19 Thread segher at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37262 Segher Boessenkool changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug rtl-optimization/37262] Two branches of the same condition being emitted

2017-11-19 Thread segher at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37262 --- Comment #8 from Segher Boessenkool --- This is fixed on trunk. I'll bisect it to see if it is worth backporting.

[Bug rtl-optimization/37262] Two branches of the same condition being emitted

2016-01-30 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37262 --- Comment #7 from Martin Sebor --- Yes, sorry, I meant to say "still there at -O1" because that's the optimization level mentioned in comment #1. (I had to guess at the level based on that. I also accidentally used -m32 when the target is pow

[Bug rtl-optimization/37262] Two branches of the same condition being emitted

2016-01-30 Thread segher at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37262 --- Comment #6 from Segher Boessenkool --- (In reply to Martin Sebor from comment #4) > I built the gcc-5-branch on powerpc64-linux and the duplicate instructions > are still there with the second test case compiled at -O2 (see below). > > $ /bu

[Bug rtl-optimization/37262] Two branches of the same condition being emitted

2016-01-29 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37262 --- Comment #5 from Martin Sebor --- To make clear what I meant by "not optimal" in comment #4, and focusing on powepc64le output with -O2 for the test case in comment #1, trunk (6.0) emits the code below. The first branch (to .L2) is superfluou

[Bug rtl-optimization/37262] Two branches of the same condition being emitted

2016-01-29 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37262 --- Comment #4 from Martin Sebor --- I confirm that there are no duplicated branch instructions in object code emitted by GCC 6.0, although the branches that are there don't look quite optimal. I built the gcc-5-branch on powerpc64-linux and the

[Bug rtl-optimization/37262] Two branches of the same condition being emitted

2015-11-22 Thread segher at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37262 Segher Boessenkool changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug rtl-optimization/37262] Two branches of the same condition being emitted

2010-03-02 Thread pinskia at gcc dot gnu dot org
--- Comment #2 from pinskia at gcc dot gnu dot org 2010-03-02 18:29 --- Still happens as of today on the trunk. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37262

[Bug rtl-optimization/37262] Two branches of the same condition being emitted

2008-08-29 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2008-08-30 01:41 --- I have seen this in other cases even for the non doloop case, though I don't know if it is because of -O1 or because it is not removing it. Testcase: int _bfd_xcoff_canonicalize_dynamic_reloc (unsigned long long l_sy

[Bug rtl-optimization/37262] Two branches of the same condition being emitted

2008-08-28 Thread pinskia at gcc dot gnu dot org
-- pinskia at gcc dot gnu dot org changed: What|Removed |Added Severity|normal |enhancement http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37262