On 04/09/2013 05:13 AM, Marek Polacek wrote:
On Tue, Apr 09, 2013 at 11:45:04AM +0200, Eric Botcazou wrote:
Alternatively, we can bump the minimum of that param, as usual ;)
Let's do that and bump it to 1, my understanding is that 0 and 1 are
equivalent for this param.
Alright. So ok to app
On Tue, Apr 09, 2013 at 11:45:04AM +0200, Eric Botcazou wrote:
> > Alternatively, we can bump the minimum of that param, as usual ;)
>
> Let's do that and bump it to 1, my understanding is that 0 and 1 are
> equivalent for this param.
Alright. So ok to apply this one (trunk/4.8)?
2013-04-09 M
> Alternatively, we can bump the minimum of that param, as usual ;)
Let's do that and bump it to 1, my understanding is that 0 and 1 are
equivalent for this param.
--
Eric Botcazou
This patch prevents two Invalid read of size 8 and one
Invalid write of size 8 warnings when cc1 is run under valgrind. What
happens here is that we firstly allocate 0B
ebb_data.path = XNEWVEC (struct branch_path,
PARAM_VALUE (PARAM_MAX_CSE_PATH_LENGTH));
(in fact, X
