On Mon, Aug 20, 2012 at 5:00 PM, Bin.Cheng wrote:
> Hi,
> Currently I am working on improving hoist pass by calculating register
> pressure and using the info to guide hoist process. It works well and
> I will send a patch once I finish it.
>
> In this work I reused codes in loop-invariant and cal
Snapshot gcc-4.6-20120824 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.6-20120824/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.6 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
Now that we have a slightly cleaner implementation of vectors,
I've been thinking of ways to fix some of the API warts:
1- Pointers vs references when handling vector elements.
Elements are sometimes passed by value (vectors of pointers) and
others they are passed by reference (vectors of objects
To take full advantage of the conversion to C++, we will need to use
single inheritance in some of our garbage collected structures. To
that end, we need to make gengtype understand single inheritance.
Here are my thoughts on how to make that happen.
There are two major sections, one for non-poly
Hi Dimitrios,
Dimitrios Apostolou skribis:
> This process proved way more tedious than it ought to be, and even
> after completing it there were some licensing issues because of GPL
> incompatibilities since I borrowed code from gnulib.
In general, Gnulib’s policy is to adjust module licenses t
> "Diego" == Diego Novillo writes:
Diego> The compiler will then always add 'file', 'function' and 'line' to the
Diego> argument list, which can then be retrieved via builtins or special
Diego> argument names (I think builtins may be safer).
Diego> This would allow us to handle operators. I
On Fri, Aug 24, 2012 at 10:01 AM, Diego Novillo wrote:
> On 2012-08-15 06:10 , Richard Guenther wrote:
>
>> Maybe have a GNU C++ builtin type
>>
>> struct __Gcc_call_location_pack {
>>const char *file;
>>const char *function;
>>unsigned line;
>> };
>>
>> and an attribute
>>
>> void foo
On 2012-08-15 06:10 , Richard Guenther wrote:
Maybe have a GNU C++ builtin type
struct __Gcc_call_location_pack {
const char *file;
const char *function;
unsigned line;
};
and an attribute
void foo (int bar) __attribute__((add_location_pack));
that directs GNU C++ to add a __Gcc_cal
