[VRP] Improve value ranges for unsigned division

2015-06-20 Thread Kugan
As discussed in PR64130, this patch improves the VRP value ranges for unsigned division. Bootstrapped and regression tested on x86_64-linux-gnu and regression tested on arm-none-linux-gnu with no new regression. Is this OK for trunk? Thanks, Kugan gcc/ChangeLog: 2015-06-20 Kugan Vivekanandara

Re: [patch] Fix two libstdc++ test failures with -std=gnu++14

2015-06-20 Thread François Dumont
On 16/06/2015 22:45, Jonathan Wakely wrote: > On 16/06/15 22:18 +0200, François Dumont wrote: >> On 12/06/2015 01:22, Jonathan Wakely wrote: >>> This fixes two test failures when the default compiler mode is >>> -std=gnu++14 >>> >>> FAIL: 25_algorithms/headers/algorithm/synopsis.cc (test for excess

Do not take address of empty string front

2015-06-20 Thread François Dumont
Hi 2 experimental tests are failing in debug mode because __do_str_codecvt is sometimes taking address of string front() and back() even if empty. It wasn't use so not a big issue but it still seems better to avoid. I propose to rather use string begin() to get buffer address. I kept operator&

[PATCH] config/bfin/bfin.c (hwloop_optimize): Set JUMP_LABEL() after emit jump_insn

2015-06-20 Thread Chen Gang
JUMP_LABLE() must be defined after optimization completed. In this case, it is doing optimization, and is almost finished, so it is no chances to set JUMP_LABLE() next. The related issue is Bug 65803. 2015-06-20 Chen Gang * config/bfin/bfin.c (hwloop_optimize): Set JUMP_LABEL() after

Re: Do not take address of empty string front

2015-06-20 Thread Jonathan Wakely
On 20/06/15 12:03 +0200, François Dumont wrote: Hi 2 experimental tests are failing in debug mode because __do_str_codecvt is sometimes taking address of string front() and back() even if empty. It wasn't use so not a big issue but it still seems better to avoid. I propose to rather use strin

Re: [PATCH, rs6000] Fix PR65914

2015-06-20 Thread Mike Stump
On Jun 19, 2015, at 5:36 PM, David Edelsohn wrote: > Maybe you should ask Richi or Jakub about the testcase because you are > placing it in a non-target-specific location. It should succeed on > all targets, but it may expose latent bugs on other targets. A latent bug is one that is broken, but