On Thu, Jan 2, 2014 at 5:10 AM, Mike Stump wrote:
> On Nov 28, 2013, at 6:20 AM, Richard Biener
> wrote:
>> On Thu, Nov 28, 2013 at 12:58 PM, Richard Sandiford
>> wrote:
>>> Jakub Jelinek writes:
On Mon, Nov 25, 2013 at 12:24:30PM +0100, Richard Biener wrote:
> On Sat, Nov 23, 2013 at
On Nov 28, 2013, at 6:20 AM, Richard Biener wrote:
> On Thu, Nov 28, 2013 at 12:58 PM, Richard Sandiford
> wrote:
>> Jakub Jelinek writes:
>>> On Mon, Nov 25, 2013 at 12:24:30PM +0100, Richard Biener wrote:
On Sat, Nov 23, 2013 at 8:21 PM, Mike Stump wrote:
> Richi has asked the we bre
On Thu, Nov 28, 2013 at 12:58 PM, Richard Sandiford
wrote:
> Jakub Jelinek writes:
>> On Mon, Nov 25, 2013 at 12:24:30PM +0100, Richard Biener wrote:
>>> On Sat, Nov 23, 2013 at 8:21 PM, Mike Stump wrote:
>>> > Richi has asked the we break the wide-int patch so that the
>>> > individual port and
Jakub Jelinek writes:
> On Mon, Nov 25, 2013 at 12:24:30PM +0100, Richard Biener wrote:
>> On Sat, Nov 23, 2013 at 8:21 PM, Mike Stump wrote:
>> > Richi has asked the we break the wide-int patch so that the
>> > individual port and front end maintainers can review their parts
>> > without have to
On Tue, Nov 26, 2013 at 9:43 AM, Jakub Jelinek wrote:
> On Mon, Nov 25, 2013 at 09:52:47PM +, Richard Sandiford wrote:
>> But my point is that at the moment we always have trees for the ranges
>> we want to record, so it seems simplest just to store those in the
>> structure. I was thinking o
On Mon, Nov 25, 2013 at 09:52:47PM +, Richard Sandiford wrote:
> But my point is that at the moment we always have trees for the ranges
> we want to record, so it seems simplest just to store those in the
> structure. I was thinking of something like the attached (only just
> started testing,
Jakub Jelinek writes:
> On Mon, Nov 25, 2013 at 09:16:24PM +, Richard Sandiford wrote:
>> > Well, the range_info_def struct right now contains 3 double_ints, which is
>> > unnecessary overhead for the most of the cases where the SSA_NAME's type
>> > has just at most HOST_BITS_PER_WIDE_INT bits
On Mon, Nov 25, 2013 at 09:16:24PM +, Richard Sandiford wrote:
> > Well, the range_info_def struct right now contains 3 double_ints, which is
> > unnecessary overhead for the most of the cases where the SSA_NAME's type
> > has just at most HOST_BITS_PER_WIDE_INT bits and thus we could fit all 3
Jakub Jelinek writes:
> On Mon, Nov 25, 2013 at 12:24:30PM +0100, Richard Biener wrote:
>> On Sat, Nov 23, 2013 at 8:21 PM, Mike Stump wrote:
>> > Richi has asked the we break the wide-int patch so that the
>> > individual port and front end maintainers can review their parts
>> > without have to
On Mon, Nov 25, 2013 at 12:24:30PM +0100, Richard Biener wrote:
> On Sat, Nov 23, 2013 at 8:21 PM, Mike Stump wrote:
> > Richi has asked the we break the wide-int patch so that the individual port
> > and front end maintainers can review their parts without have to go through
> > the entire patc
On Sat, Nov 23, 2013 at 8:21 PM, Mike Stump wrote:
> Richi has asked the we break the wide-int patch so that the individual port
> and front end maintainers can review their parts without have to go through
> the entire patch.This patch covers the gimple code.
>
> Ok?
@@ -1754,7 +1754,7 @@
Richi has asked the we break the wide-int patch so that the individual port and
front end maintainers can review their parts without have to go through the
entire patch.This patch covers the gimple code.
Ok?
* gimple.c
(preprocess_case_label_vec_for_gimple): Use wide-int int
12 matches
Mail list logo
