Hello everyone,
I am struggling to build h8300 crosscompiler from GCC4.4.0.
I learned it is necessary to patch gcc for complying to double 64 bits.
I used next sources.
binutils-2.19.1.tar.bz2
gcc-4.4.0.tar.bz2
newlib-1.17.0.tar.gz
I've got patch for GCC3.3.2 source.
I appended it in compressed
Concepts have recently been removed from the C++0x Standard Draft.
Will the concepts branch be discontinued?
On Tue, Jul 28, 2009 at 3:01 AM, Piotr Wyderski wrote:
> Concepts have recently been removed from the C++0x Standard Draft.
> Will the concepts branch be discontinued?
I hope not. Concepts will be "finished" and re-added to C++, and it
would be immensely helpful in that effort if there were a ver
Thanks David.
I thought -mmininal-toc might have been a better workaround as well :-) .
Is there a Bugzilla number for this issue?
-Original Message-
From: David Edelsohn [mailto:dje@gmail.com]
Sent: Tuesday, July 28, 2009 9:46 AM
To: Tim Crook
Subject: Re: How to figure out the gcc
James Dennett wrote:
On Tue, Jul 28, 2009 at 3:01 AM, Piotr Wyderski wrote:
Concepts have recently been removed from the C++0x Standard Draft.
Will the concepts branch be discontinued?
I hope not. Concepts will be "finished" and re-added to C++, and it
would be immensely helpful in th
On Tue, Jul 28, 2009 at 10:44 AM, Tim Crook wrote:
> Thanks David.
>
> I thought -mmininal-toc might have been a better workaround as well :-) .
>
> Is there a Bugzilla number for this issue?
I believe this was GCC Bugzilla Bug 24779. It partially was fixed in
GCC 4.1, but not fully fixed until D
Ed Smith-Rowland wrote:
James Dennett wrote:
On Tue, Jul 28, 2009 at 3:01 AM, Piotr
Wyderski wrote:
Concepts have recently been removed from the C++0x Standard Draft.
Will the concepts branch be discontinued?
I hope not. Concepts will be "finished" and re-added to C++, and it
would be
> > struct cgraph_edge *edge = cgraph_edge (id->src_node,
> > orig_stmt);
> POINT_A
> > int flags;
> >
> > switch (id->transform_call_graph_edges)
> >{
> > case CB_CGE_DUPLICATE:
> >if (edge)
> >
On 07/28/2009 10:16 AM, Jan Hubicka wrote:
There is code in cgraph_copy_node_for_versioning that redirect callers
in the list to new location. Since clonning might render some code
unreachable and remove edges, this can lead to ICE. But since this
was formely invented for IPA-CP, that is now us
Apologies if you receive multiple copies of this call.
CALL FOR PAPERS
2nd Workshop on
GCC Research Opportunities
2009/7/28 Basile STARYNKEVITCH:
>
> It could perhaps be not a branch, but a plugin, but I know not much about
> C++ concepts, and absolutely nothing about the existing C++ concepts
> branch[es].
I don't think that would work - the standard library changes that go
along with the language feature co
Snapshot gcc-4.4-20090728 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.4-20090728/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.4 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
On 07/28/2009 10:44 AM, Richard Henderson wrote:
I guess I'll poke at cleaning this up today. I've got to
familiarize myself with how virtual clones work...
The virtual clones that ipa-cp makes seems to be easy.
My thought here is that since (virtual) clones don't
have actual bodies (and when
On s390x it produces this insn:
(insn 8 7 9 3 323444.c:15 (set (mem/s:DI (reg:DI 46) [0 S8 A64])
(mem/s:DI (reg/v/f:DI 45 [ tp ]) [0 S8 A64])) -1 (nil))
Note that the alignments are 64 bit again, despite the field being
packed. mep-elf has similar results.
void *memcpy(void *dest, co
> On 07/28/2009 10:44 AM, Richard Henderson wrote:
> >I guess I'll poke at cleaning this up today. I've got to
> >familiarize myself with how virtual clones work...
>
> The virtual clones that ipa-cp makes seems to be easy.
>
> My thought here is that since (virtual) clones don't
> have actual bo
15 matches
Mail list logo
