> the code was in Google code I think, his porting instructions should work for
> the latest gawk too.
was, as in google code is dead.
- erik
> One potential big future change (not yet made) is to switch to
> strictly ANSI rules for unsigned+signed values meeting in "the usual
> arithmetic conversions". The rules are horrible, but it's one of the
> few ways in which the compiler implements something that's neither an
> extension nor a r
On Thu Mar 12 11:10:17 PDT 2015, chneukirc...@gmail.com wrote:
> erik quanstrom writes:
>
> > so an interesting problem i run into from time to time is separately
> > computing
> > the files added to and deleted from a directory in a shell script. uniq
> > doesn't
> > work for this. certainly
erik quanstrom writes:
> so an interesting problem i run into from time to time is separately computing
> the files added to and deleted from a directory in a shell script. uniq
> doesn't
> work for this. certainly one can loop over two lists of files and do
> this easily,
> but that seems dul
On Thu, Mar 12, 2015 at 3:50 AM, Aram Hăvărneanu wrote:
> On Wed, Mar 11, 2015 at 10:04 PM, Ryan Gonzalez wrote:
> > Go had vastly better versions, but it seems they got ripped out
> recently. I
> > think Go 1.3 may have had them, in which case you'd do something like:
> >
> > go tool 6c tst.c
>
I know. I'm referring to the ken-cc port.
On Thu, Mar 12, 2015 at 3:51 AM, Aram Hăvărneanu wrote:
> On Wed, Mar 11, 2015 at 10:04 PM, Ryan Gonzalez wrote:
> > As you can see, Go actually had a working 64-bit compiler.
>
> Plan 9 and Inferno have working 64-bit compilers. They are used for
> the
On Thu Mar 12 10:09:06 PDT 2015, minux...@gmail.com wrote:
> On Mar 12, 2015 12:52 PM, "erik quanstrom" wrote:
> > so an interesting problem i run into from time to time is separately
> computing
> > the files added to and deleted from a directory in a shell script. uniq
> doesn't
> > work for t
That reminds me that I've got various small repairs and changes to merge in.
Possibly the best way will be to point to a test version in an announcement
here, and
then people can check that they work for them, so nothing breaks
unexpectedly on
recompilation.
One potential big future change (not ye
On Mar 12, 2015 12:52 PM, "erik quanstrom" wrote:
> so an interesting problem i run into from time to time is separately
computing
> the files added to and deleted from a directory in a shell script. uniq
doesn't
> work for this. certainly one can loop over two lists of files and do
this easily,
so an interesting problem i run into from time to time is separately computing
the files added to and deleted from a directory in a shell script. uniq doesn't
work for this. certainly one can loop over two lists of files and do this
easily,
but that seems dull and tedious.
but as it turns out,
Thanks Charles. I agree completely and will add that they will pry Ken's
compilers, so wonderfully supported by you, from my cold, dead fingers. South
Suite's new kernel will always be compiled with 6c. As far as performance
goes, to paraphrase Chuck Yeager, it's not the compiler, it's the co
On 12 March 2015 at 10:06, Charles Forsyth
wrote:
> I've used it and lib9 in several other projects where other compilers
> couldn't be used for licensing reasons, or because they were awful.
>
I'll add that the compilers are great for kernel and other New World
systems work.
Once stable on a gi
On 12 March 2015 at 08:51, Aram Hăvărneanu wrote:
> Plan 9 and Inferno have working 64-bit compilers.
Periodically I pull the Plan 9 and Inferno variants into line, so they
should be about the same.
It's one reason I split off the Thumb implementation, although it handled
ARM/Thumb interlinking
Thanks for the link to the Google code repo.
I'm currently on x86_64 Ubuntu 12.04. Building was not so smooth, several
files are missing for the Power 64 port.
I did as best I could to build things. I suppose my expectations aren't
what they should be. I was looking for the usual
config
On Wed, Mar 11, 2015 at 10:04 PM, Ryan Gonzalez wrote:
> As you can see, Go actually had a working 64-bit compiler.
Plan 9 and Inferno have working 64-bit compilers. They are used for
the many Plan 9 amd64 kernels. Go's C compilers all came from Inferno,
including 6c.
--
Aram Hăvărneanu
On Wed, Mar 11, 2015 at 10:04 PM, Ryan Gonzalez wrote:
> Go had vastly better versions, but it seems they got ripped out recently. I
> think Go 1.3 may have had them, in which case you'd do something like:
>
> go tool 6c tst.c
> go tool 6l -o tst tst.6
First, Go did not have "vastly better versio
16 matches
Mail list logo
