On Wed, Apr 20, 2011 at 9:06 PM, Xinliang David Li wrote:
> On Wed, Apr 20, 2011 at 12:03 PM, Cary Coutant wrote:
>>> This brings out 2 questions. Why don't GCC 4.4/4.6/4.7 warn it?
>>> Why doesn't 64bit GCC 4.2 warn it?
>>
>> Good question. It seems that the difference is whether the compiler
>
Status
==
A first release candidate for GCC 4.5.3 is beeing made. The branch
is now frozen until after the final 4.5.3 release. All changes
require explicit release manager approval.
Quality Data
Priority # Change from Last Report
--- ---
On Thursday 21 April 2011 11:30:49 Richard Guenther wrote:
> Status
> ==
>
> A first release candidate for GCC 4.5.3 is beeing made. The branch
> is now frozen until after the final 4.5.3 release. All changes
> require explicit release manager approval.
>
>
> Quality Data
>
>
A first release candidate for GCC 4.5.3 is available from
ftp://gcc.gnu.org/pub/gcc/snapshots/4.5.3-RC-20110421/
and shortly its mirrors. It has been generated from SVN revision 172803.
I have sofar bootstrapped and tested the release candidate on
x86_64-unknown-linux-gnu. Please test it
Hi Ian,
Ian Lance Taylor writes:
> Boris Kolpackov writes:
>
> > Yes, that's what I suspect. Which is unfortunate since GCC already creates
> > all the nodes. All that is left is to establish a link between two types.
> > While this is not necessary for C/C++ compilation, it could be useful for
Boris Kolpackov writes:
> I was also thinking if adding an extra member would be a big deal,
> memory usage-wise. This member is only going to be added to the
> TYPE nodes (struct tree_type). I may be wrong, but I would expect
> that there aren't that many such nodes in a typical translation
> un
Does any processor besides the PowerPC support varients of the prefetch
instruction that you can tell it that there are hardware streams with a given
stride at the beginning of the loop, rather than doing a prefetch inside the
loop for a future cache entry?
I'm just starting to look at adding supp
On Thu, Mar 31, 2011 at 01:32:24PM +0100, Paulo J. Matos wrote:
> On 30/03/11 08:57, Claudiu Zissulescu wrote:
> >Hi,
> >
> >I would try using the named address space for your issue (see
> >TARGET_ADDR_SPACE_POINTER_MODE). Please check the SPU target for an
> >implementation example.
> >
>
> Hummm
Ian Lance Taylor writes:
> Boris Kolpackov writes:
>
> > I was also thinking if adding an extra member would be a big deal,
> > memory usage-wise. This member is only going to be added to the
> > TYPE nodes (struct tree_type). I may be wrong, but I would expect
> > that there aren't that many s
Snapshot gcc-4.5-20110421 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.5-20110421/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.5 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
Recently, we tried to merge the GCC trunk into the GUPC branch
and ran into an issue caused by a recent GCC update.
The last successful merge was trunk version 172359, fyi.
For certain UPC file scope static initializers,
a per file initialization routine is created, its address
is added to a glob
11 matches
Mail list logo