I think the main reason is that DMD front end sources are dual licensed
with GPL and Artistic License. The DMD backend is not under an open
source license (personal use only), so the Artistic License is how the
two are integrated. The fork is required to allow DMD to continue under
its current
On 01/23/2010 04:29 PM, Richard Guenther wrote:
We could warn about this when building with C++ but with C we do not
see bools but ints here.
With such a warning there would be no reason not to build stage2 and
stage3 with bool == _Bool.
Paolo
On Sun, Jan 24, 2010 at 07:00:44AM -0800, Paolo Bonzini wrote:
> > I think the main reason is that DMD front end sources are dual licensed
> > with GPL and Artistic License. The DMD backend is not under an open
> > source license (personal use only), so the Artistic License is how the
> > two are
Strictly speaking, that's not true. Even if the submitter would still
be required to have copyright assignment for the FSF, they could be
copyable to the DMD front-end _as long as the submitter himself sends
them for inclusion there too_. This is the practical significance of
the license grant
Richard,
Could you provide us with a good reference for the latencies and other
speed issues of SSE operations? What I've found is scattered and hard
to compare.
Frankly, I was under the misconception that each of these SSE operatons
was meant to be accomplished in a single clock cycle (although
On Sun, Jan 24, 2010 at 10:32 PM, Steve White wrote:
> Richard,
>
> Could you provide us with a good reference for the latencies and other
> speed issues of SSE operations? What I've found is scattered and hard
> to compare.
>
> Frankly, I was under the misconception that each of these SSE operat
Steve White wrote:
I was under the misconception that each of these SSE operatons
was meant to be accomplished in a single clock cycle (although I knew there
are various other issues.)
Current CPU architectures permit an SSE scalar or parallel multiply and
add instruction to be issued on eac
Snapshot gcc-4.3-20100124 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.3-20100124/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.3 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
This is to report a successful build of GCC 4.4.3 and GCC 4.5.0
(156177) on my Macbook6,1.
./config.guess:
i386-apple-darwin10.2.0
gcc -v:
For GCC 4.4.3:
Using built-in specs.
Target: x86_64-apple-darwin10.2.0
Configured with: ../gcc-4.4.3/configure
--prefix=/Users/olexa/Documents/MyApps/Comm
