Hi,
I'm pleased to announce that AMD (1) donated two 12-cores Magny-Cours
processors running at 1.5 GHz to the GCC Compile Farm project (2) and
that FSF France (3) funded the purchase of the rest of the machine,
including 64GB of RAM, 2TB of disk and 80 GB of SSD.
The machine, named gcc10, has b
Hello all,
I am trying to port GCC 4.5.1 for a processor that has the following
addressing capability:
The data memory address space of 64K bytes is represented by a total
of 15 bits, with each address selecting a 16-bit element. When using
the address register, the LSB of address reg (AD) points
Hi,
On Mon, 16 Aug 2010, Mohamed Shafi wrote:
> Hello all,
>
> I am trying to port GCC 4.5.1 for a processor that has the following
> addressing capability:
>
> The data memory address space of 64K bytes is represented by a total
> of 15 bits, with each address selecting a 16-bit element. When
On Mon, Aug 16, 2010 at 2:10 PM, Mohamed Shafi wrote:
> Hello all,
>
> I am trying to port GCC 4.5.1 for a processor that has the following
> addressing capability:
>
> The data memory address space of 64K bytes is represented by a total
> of 15 bits, with each address selecting a 16-bit element.
On 16/08/2010 14:16, Michael Matz wrote:
> Hi,
>
> On Mon, 16 Aug 2010, Mohamed Shafi wrote:
>
>> Hello all,
>>
>> I am trying to port GCC 4.5.1 for a processor that has the following
>> addressing capability:
>>
>> The data memory address space of 64K bytes is represented by a total
>> of 15 bit
On Sun, 15 Aug 2010 04:45:53 -0400
Robert Dewar wrote:
> I think there is a difference between a novel you can hold and
> read, and computer documentation. My question was not whether
> anyone reads books any more, it was whether people read computer
> manuals in this form any more.
Just as a ra
Quoting Miles Bader :
With elisp, I've found that in practice I usually start by copying the
docstring (the "in code doc") to the manual (the "doc doc"), but almost
always end up largely rewriting to fit the context in the manual better,
and to explain things in more detail (modern docstrings te
> > With elisp, I've found that in practice I usually start by copying the
> > docstring (the "in code doc") to the manual (the "doc doc"), but almost
> > always end up largely rewriting to fit the context in the manual better,
> > and to explain things in more detail (modern docstrings tend to be
Quoting Richard Kenner :
Unless one can claim "fair use". But the above procedure is also likely
to result in taking nothing copyrightable from the original text anyway.
But fair use does not apply here (geographically), and I don't want to
have to consult a copyright lawyer to verify if I ca
James Dennett writes:
> Apart from using the name gcc@gcc.gnu.org for the help list, and
> gcc-...@gcc.gnu.org for developers (who should be able to find the
> right list)?
I tend to agree that we should change the name of the gcc@gcc.gnu.org
mailing list.
Ian
10 matches
Mail list logo
