On Fri, May 22, 2015 at 04:56:57PM +, Taylor R Campbell wrote:
>Date: Fri, 22 May 2015 13:09:58 +0100
>From: Patrick Welche
>
>There are a load of locking PRs involving vnd. I thought I would have a
>stab at converting vnd to use condvars and mutexes (mutices?) as a first
>
Antti Kantee wrote:
> On 31/05/15 06:05, matthew green wrote:
> > hi Andrew! :)
> >
> >> Who is appalled to discover that pc532 support has been removed!
>
> In addition to toolchain support, the hardware was near-extinct at the
> time of removal.
That prompted me to turn the old beast on. Apa
On 1 June 2015 at 02:15, Anders Magnusson wrote:
> Andrew Cagney skrev den 2015-06-01 03:24:
>>
>> systems and generates reasonable code. Unfortunately, and sorry PCC
>> (stabs, really?),
>
> Feel free to add dwarf, the source is out there, and it wouldn't be
> especially difficult to do it. I j
On Mon, Jun 01, 2015 at 11:41:38AM -0400, Andrew Cagney wrote:
> >> systems and generates reasonable code. Unfortunately, and sorry PCC
> >> (stabs, really?),
> >
> > Feel free to add dwarf, the source is out there, and it wouldn't be
> > especially difficult to do it. I just haven't had tim
On Sun, May 31, 2015 at 09:24:48PM -0400, Andrew Cagney wrote:
> On 30 May 2015 at 19:09, David Holland wrote:
> > The reason I floated the idea of forking is that an OS that's
> > specifically intended to be a high-quality Unix for older hardware can
> > make a different set of decisions (mos
On 1 June 2015 at 12:54, David Holland wrote:
> On Mon, Jun 01, 2015 at 11:41:38AM -0400, Andrew Cagney wrote:
> > >> systems and generates reasonable code. Unfortunately, and sorry PCC
> > >> (stabs, really?),
> > >
> > > Feel free to add dwarf, the source is out there, and it wouldn't be
>
On 1 June 2015 at 13:50, David Holland wrote:
> but ignoring that -- who (other than apparently the gcc development
> team) is focusing on burning ram?
GNU, this is from the GNU coding standard; to me it explains some of
the design choices I find in many GNU utilities:
"For example, Unix utiliti
> > (oh and please delete C++ groff, just replace it with that AWK script)
>
> which awk script? :-)
>
> (quite seriously, I've been looking for a while for an alternative to
> groff for typesetting the miscellaneous articles in base.
I was thinking of http://doc.cat-v.org/henry_spencer/awf/ whi
On Mon, 1 Jun 2015, Andrew Cagney wrote:
> PCC, as a "classic" C compiler, only generates debug information at
> -O0. This this is because the stabs code is restricted to the
> un-optimized code generator path.
this is not actually the case btw, and I don't recall it being like that
in the last
On 5/30/15 6:16 PM, David Holland wrote:
> My thought is that rather than shim layers we (fsvo "we") ought to be
> aggressively producing an alternative design, with the goal of getting
> it to the point where application developers take notice instead of
> robotically following where gnome/kde lea
On Mon, Jun 01, 2015 at 05:50:07PM +, David Holland wrote:
> On Sun, May 31, 2015 at 09:24:48PM -0400, Andrew Cagney wrote:
>
> > (oh and please delete C++ groff, just replace it with that AWK script)
>
> which awk script? :-)
>
> (quite seriously, I've been looking for a while for an alte
On 1 June 2015 at 15:13, Iain Hibbert wrote:
> On Mon, 1 Jun 2015, Andrew Cagney wrote:
>
>> PCC, as a "classic" C compiler, only generates debug information at
>> -O0. This this is because the stabs code is restricted to the
>> un-optimized code generator path.
>
> this is not actually the case
At Fri, 29 May 2015 10:22:35 +, David Holland
wrote:
Subject: Re: Removing ARCNET stuffs
>
> There's one other thing I ought to mention here, which is that I have
> never entirely understood the point of running a modern OS on old
> hardware; if you're going to run a modern OS, you can run i
13 matches
Mail list logo
