On 27 Feb 2019, at 18:37, Richard Kenner wrote:
>
> 1) Whether executing a program is considered making a copy under
> copyright law.
I had a look through some of the published judgements, and it's clear that in
the US at least copying into RAM (for whatever purpose, and provided the copy
has
On 27 Feb 2019, at 12:41, Richard Kenner wrote:
>
> Remember that, from the perspective of copyright law, executing a program is
> making a "copy"
> of that program.
Has that (rather extreme) view been litigated?
On 5 Jul 2018, at 20:08, Richard Biener wrote:
>
> On July 5, 2018 6:37:58 PM GMT+02:00, Martin Sebor wrote:
>> Ada tests don't seem to respond to the INT signal: when
>> I interrupt a parallel make check while the Ada tests are
>> running, other test suites are interrupted as well and go
>> awa
On 27 Feb 2018, at 17:07, Torvald Riegel wrote:
>
> On Tue, 2018-02-27 at 16:40 +, Simon Wright wrote:
>> On 27 Feb 2018, at 12:56, Ruslan Nikolaev via gcc wrote:
>>>
>>> And all this mess to accommodate almost non-existent case when someone
>>>
On 27 Feb 2018, at 12:56, Ruslan Nikolaev via gcc wrote:
>
> And all this mess to accommodate almost non-existent case when someone wants
> to use atomic_load on read-only memory for wide types, in which no good
> solution exists anyway
Sorry to butt in, but - if it's ROM why would you need at
On 7 Jul 2017, at 22:31, Martin Sebor wrote:
>
> I see large numbers of timeouts in Ada tests on trunk in parallel
> run s (make -j96) on x86_64. Messages like the one below appear
> in the logs, suggesting some sort of heap corruption. I'm having
> trouble reproducing it outside the rest of th
On 11 May 2017, at 11:50, Kyrill Tkachov wrote:
> On 11/05/17 11:43, Simon Wright wrote:
>> I see from https://gcc.gnu.org/install/test.html that it's possible to run
>> tests in parallel. I get the impression from gcc/Makefile that the check
>> concerned has to be
I see from https://gcc.gnu.org/install/test.html that it's possible to run
tests in parallel. I get the impression from gcc/Makefile that the check
concerned has to be set up in the Makefile (in my build tree, configured with
--target=x86_64-apple-darwin16
--enable-languages=c,c++,ada,fortran,o
I see that, in the GCC 7 Release Criteria, the Secondary Platforms list
includes i686-apple-darwin.
Should this now be x86_64-apple-darwin? I've been building this since GCC
4.5.0, Darwin 10, in 2011.
The Mercurial mirror at http://gcc.gnu.org/hg/gcc was last updated 11 months
ago at SVN r166522.
I think it can only cause confusion to have the mirror live but stale; ought it
to be turned off?
The Mercurial mirror at http://gcc.gnu.org/hg/gcc was last updated 11 months
ago at SVN r166522.
I think it can only cause confusion to have the mirror live but stale; ought it
to be turned off?
In http://gcc.gnu.org/onlinedocs/, the Current development / User-
Level Documentation link to GNAT User's Guide is broken.
12 matches
Mail list logo