On Wed, Apr 10, 2013 at 06:42:58PM +0200, Marek Polacek wrote:
> On Wed, Apr 10, 2013 at 11:49:18AM +0200, Jakub Jelinek wrote:
> > Shouldn't this be again solved instead by bumping minimum for the param to 1
> > from 0? Because, the smaller the param is, the bigger freq_threshold is,
> > so if fo
On Wed, Apr 10, 2013 at 11:49:18AM +0200, Jakub Jelinek wrote:
> Shouldn't this be again solved instead by bumping minimum for the param to 1
> from 0? Because, the smaller the param is, the bigger freq_threshold is,
> so if for the smallest param we suddenly set freq_threshold to 0, it isn't
> co
On Wed, Apr 10, 2013 at 11:44:18AM +0200, Marek Polacek wrote:
> Ping.
>
> On Thu, Apr 04, 2013 at 04:01:09PM +0200, Marek Polacek wrote:
> > This fixes an ICE in case we use weirdo --param value for
> > PARAM_ALIGN_THRESHOLD. The patch is by Andrew; I added CL, testcase
> > and tested.
> >
> >
Ping.
On Thu, Apr 04, 2013 at 04:01:09PM +0200, Marek Polacek wrote:
> This fixes an ICE in case we use weirdo --param value for
> PARAM_ALIGN_THRESHOLD. The patch is by Andrew; I added CL, testcase
> and tested.
>
> Bootstrapped/regtested on x86_64-linux, ok for trunk? And what about other
>
This fixes an ICE in case we use weirdo --param value for
PARAM_ALIGN_THRESHOLD. The patch is by Andrew; I added CL, testcase
and tested.
Bootstrapped/regtested on x86_64-linux, ok for trunk? And what about other
branches?
2013-04-04 Marek Polacek
Andrew Pinski
PR tre
