From: Richard Sandiford
Date: Mon, 29 Oct 2012 10:14:53 +
> ...given that the code is like you say written:
>
> if (SHIFT_COUNT_TRUNCATED)
> {
> if (CONST_INT_P (op1)
> ...
> else if (GET_CODE (op1) == SUBREG
> && subreg_lowpart_p (op1)
> &
On 15/11/2012, at 10:39 PM, Alexander Ivchenko wrote:
>>> The canonical way of building native applications for Android is to add
>>> -fno-pic to the compiler flags.
> That’s true for programs in userspace, but for Android system-level
> programs (standalone executables) like system tools, consol
As we continue adding new C++ features in the compiler, gengtype
is becoming an increasing source of pain. In this proposal, we
want to explore different approaches to GC that we could
implement.
At this point, we are trying to reach consensus on the general
direction that we should take. Given
On 11/15/12, Michael Matz wrote:
> On Wed, 14 Nov 2012, Lawrence Crowl wrote:
> > Diego and I seek your comments on the following (loose) proposal.
>
> In principle I agree with the goal, I'm not sure I like the
> specific way yet, and even if I do I have some suggestions:
>
> > We will add a set
On 11/14/12, Basile Starynkevitch wrote:
> On Wed, Nov 14, 2012 at 05:13:12PM -0800, Lawrence Crowl wrote:
>> Diego and I seek your comments on the following (loose) proposal.
>>
>>
>> Generating gimple and tree expressions require lots of detail,
>> which is hard to remember and easy to get wrong
On 11/14/12, Andrew Pinski wrote:
> On Nov 14, 2012, Lawrence Crowl wrote:
>> Diego and I seek your comments on the following (loose) proposal.
>>
>>
>> It is sometimes hard to remember which printing function is used
>> for debugging a type, or even which type you have.
>>
>> We propose to rely
On 14.11.12 21:57, Peter Bergner wrote:
> On Wed, 2012-11-14 at 18:51 +0100, Andreas Tobler wrote:
>> Hello,
>>
>> on trunk (193501) I get a comparison failure:
>> ---
>> Bootstrap comparison failure!
>> gcc/tree-ssa-forwprop.o differs
>> ---
>>
>> This is with --disable-checking. Leaving disable-c
On Thu, Nov 15, 2012 at 9:01 AM, Michael Matz wrote:
> Hi,
>
> On Thu, 15 Nov 2012, Gabriel Dos Reis wrote:
>
>> On Thu, Nov 15, 2012 at 8:48 AM, Michael Matz wrote:
>> [...]
>> > The method name should imply the action, e.g. 'add_stmt' or append_stmt
>> > or the like.
>>
>> strongly agreed.
>> [
Hi,
On Thu, 15 Nov 2012, Gabriel Dos Reis wrote:
> On Thu, Nov 15, 2012 at 8:48 AM, Michael Matz wrote:
> [...]
> > The method name should imply the action, e.g. 'add_stmt' or append_stmt
> > or the like.
>
> strongly agreed.
> [...]
>
> > All in all I think we can severely improve on building
On Thu, Nov 15, 2012 at 8:48 AM, Michael Matz wrote:
[...]
> The method name should imply the action, e.g. 'add_stmt' or append_stmt
> or the like.
strongly agreed.
[...]
> All in all I think we can severely improve on building gimple statements
> without introduction of any helper class. Basic
Hi Lawrence,
On Wed, 14 Nov 2012, Lawrence Crowl wrote:
> Diego and I seek your comments on the following (loose) proposal.
In principle I agree with the goal, I'm not sure I like the specific way
yet, and even if I do I have some suggestions:
> We will add a set of helper classes to be used a
>> The canonical way of building native applications for Android is to add
>> -fno-pic to the compiler flags.
That’s true for programs in userspace, but for Android system-level
programs (standalone executables) like system tools, console apps or
tests it seems -fpic doesn’t make much sense.
>> T
12 matches
Mail list logo
